[
https://issues.apache.org/jira/browse/PROTON-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921823#comment-17921823
]
Andrew Stitcher commented on PROTON-2531:
-----------------------------------------
Since the only values you can get in a bytes object are 0x00-0xff and latin-1
just translates them directly into the same unicode codepoint and they are all
valid codepoints in unicode I think latin-1 is the correct decoder to use.
The raw_unicode_escape probably gives the same result since none of the imput
codepoints need encoding in unicode anyway. Unless I'm misunderstanding/getting
encoding/decoding confused - man, I hate dealing with unicode in python!
Does that make sense?
I think adding some tests to check a better selection of tags is a good idea.
> Delivery tag is str while it should be bytes
> --------------------------------------------
>
> Key: PROTON-2531
> URL: https://issues.apache.org/jira/browse/PROTON-2531
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Reporter: Ievgen Popovych
> Priority: Major
>
> According to AMQP standard delivery tag is ??up to 32 octets of binary
> data??. Proton C library also has it in binary format.
> But in the Python binding {{Delivery.tag}} is a string, which causes issues
> when trying to use it (i.e. print/visualize).
> As far as I understand this is down to Swig {{python/cproton.i}}
> {{wrap_pn_delivery_tag}} (since typemap for {{pn_delivery_tag_t}} seems to be
> correct)?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
