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 pitrou
Recipients christian.heimes, fijall, hynek, loewis, ncoghlan, petri.lehtinen, pitrou, python-dev
Date 2012-06-15.12:53:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339764611.3399.7.camel@localhost.localdomain>
In-reply-to <4FDB2BC7.20703@cheimes.de>
Content
> > The point of supporting unicode would precisely be to avoid a
> > unicode->bytes conversion when unicode strings are received.
> 
> A byte-wise comparison of the memory representation would work IFF both
> sides have the same type and unicode kind. Anything else could give away
> details of the content.

My proposal was to only allow them on ASCII strings. Any other unicode
kind would raise an error (perhaps NotImplementedError).
History
Date User Action Args
2012-06-15 12:53:15pitrousetrecipients: + pitrou, loewis, ncoghlan, christian.heimes, fijall, python-dev, petri.lehtinen, hynek
2012-06-15 12:53:15pitroulinkissue15061 messages
2012-06-15 12:53:15pitroucreate