This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Tom.Christie
Recipients Tom.Christie, georg.brandl, r.david.murray
Date 2014-10-30.20:16:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414700169.99.0.281263691513.issue22767@psf.upfronthosting.co.za>
In-reply-to
Content
> So, as soon as (but only as soon as) you mix unicode with your non-ascii data, your program blows up.

Indeed. For context tho my example of running into this the unicode literals used as seperators weren't even in the same package as the non-ASCII binary strings. (JSONRenderer in Django REST framework, being excersized by some third party test code. End result non-obvious exception.

Anyways, okay with this resolution, although I am now using a compat branch to ensure that we use binary seperators in py2 to continue to get the more lax rendering style.
History
Date User Action Args
2014-10-30 20:16:10Tom.Christiesetrecipients: + Tom.Christie, georg.brandl, r.david.murray
2014-10-30 20:16:09Tom.Christiesetmessageid: <1414700169.99.0.281263691513.issue22767@psf.upfronthosting.co.za>
2014-10-30 20:16:09Tom.Christielinkissue22767 messages
2014-10-30 20:16:09Tom.Christiecreate