You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/02/09 15:40:18 UTC
[jira] [Commented] (PROTON-1061) [Python Binding] Add support for
all AMQP 1.0 types
[ https://issues.apache.org/jira/browse/PROTON-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139003#comment-15139003 ]
ASF subversion and git services commented on PROTON-1061:
---------------------------------------------------------
Commit 5ada2ec00b30b67d4f182d6c418011c0b77ca1ca in qpid-proton's branch refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5ada2ec ]
PROTON-1061: Fixed error in Python binding in which int types were mapped to AMQP type long.
> [Python Binding] Add support for all AMQP 1.0 types
> ---------------------------------------------------
>
> Key: PROTON-1061
> URL: https://issues.apache.org/jira/browse/PROTON-1061
> Project: Qpid Proton
> Issue Type: Task
> Components: python-binding
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> Currently, a number of AMQP 1.0 simple types are not supported in the Python binding. Only those types that "make sense" from a Python language point-of-view are currently supported, but types such as the unsigned integral types, 32-bit float and the decimal types are not supported. As long as the Python client only talks to other Python clients, this approach makes sense, but as soon as a Python client needs to talk to some other client that may require these types, then an impasse is reached.
> The AMQP types currently *NOT* supported in the Python binding are:
> * Byte
> * Short
> * Int (32-bit)
> * Ubyte
> * Ushort
> * Uint (32-bit)
> * Float (32-bit)
> * Decimal32
> * Decimal64
> * Decimal128
> A proposed patch is available for review at https://reviews.apache.org/r/39479/.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)