[ 
https://issues.apache.org/jira/browse/PROTON-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088265#comment-15088265
 ] 

ASF subversion and git services commented on PROTON-1061:
---------------------------------------------------------

Commit 97f93b9d4657de620818dd170f438245dc8d846e in qpid-proton's branch 
refs/heads/go1 from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=97f93b9 ]

PROTON-1061: [Python Binding] Add support for all AMQP 1.0 types


> [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)

Reply via email to