-
Notifications
You must be signed in to change notification settings - Fork 18
Handle marshaling and emitting unicode encoded byte strings #16
Comments
Hi @jashugan As a basic sanity check I verified that this unicode string in the corrected form The behavior you're observing is related to an additional
This matches Python's literal behavior and produces human readable unicode:
I'm going to investigate this further to determine what behavior we want here. The error producing cases are almost certainly a deficiency. Did you encounter this as a bug through a means other than interactive use? |
@benkamphaus. Yes, I discovered this bug in our app. I wanted to send the above string via transit+json, but got an error with urllib. |
Hi @jashugan Just to summarize our findings (and future actions on this):
As such, I'm going to label this issue as an enhancement request for handling unicode encoded byte strings. |
I'm having problems encoding unicode correctly when using transit. I would expect that it would work similarly to the json encoder when using transit with the json encoder. Note below that when encoding a unicode string the json encoder consistently provides the same output. The transit encoder fails on the last two variations and produces different output from the json encoder on the first variation.
The text was updated successfully, but these errors were encountered: