On 6/5/2014 11:41 AM, Daniel Holth wrote: > discover new things > like dance-encoded strings, bytes decoded using an incorrect encoding > intended to be transcoded into the correct encoding later, surrogates > that work perfectly until .encode(), str(bytes), APIs that disagree > with you about whether the result should be str or bytes, APIs that > return either string or bytes depending on their initializers and so > on. Unicode can still be complicated in Python 3 independent of any > judgement about whether it is worse, better, or different than Python > 2. Yes, people can find ways to write bad code in any language. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140605/4c3594ca/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4