News for hackers. Stuff that matters.
Re:Python 2.x vs 3.x use survey by Kliment on Tuesday December 31, 2013 @10:28AM (#6990888)
The inability to use string manipulation functions on bytestrings without converting them to unicode and back for each operation.
Re:Python 2.x vs 3.x use survey by viraptor on Tuesday December 31, 2013 @10:35AM (#6990926)
What do you mean by "string manipulation"? bytes are not text strings. If you actually mean text operations, then converting them is something you should also do in py2.

Edit: now that I thought about it - since you're able to decode the bytes you're using, it means you are operating on text - why not convert it then?

Re:Python 2.x vs 3.x use survey by Kliment on Tuesday December 31, 2013 @02:11PM (#6992246)
See http://bugs.python.org/issue3982 that's linked elsewhere in these comments for the kind of things that don't work on bytestrings
Re:Python 2.x vs 3.x use survey by viraptor on Tuesday December 31, 2013 @08:30PM (#6993749)
I read it all, and to be honest I think I agree the most with http://bugs.python.org/issue3982#msg180441 (.format may be making some things simpler, but it goes against the idea of well separated bytes -vs- text)

But really, I just don't like how http/ftp/similar protocols were designed in the first place. They're mixing binary and text in the same stream. That's ugly and when you have strict rules about text encoding in your language, the implementation also turns out ugly - what a surprise :)

Re:Python 2.x vs 3.x use survey by Borogove on Tuesday December 31, 2013 @04:09PM (#6992854)
As many comments in that thread point out, byte arrays are not strings, and casually conflating or implicitly converting the two is terrible mental hygiene.

Explicit is better than implicit.