News for hackers. Stuff that matters.
Re:Python 2.8 Un-release Schedule by Daishiman on Tuesday March 13, 2012 @02:21AM (#3697254)
Whoa whoa, Unicode is huge for users of internationalized libraries and internationalization packages. I think you're underestimating the importance of this.

JIT and GIL are not language features, they're implementation details. Once alternative implementations catch up, many will look at this again.

The other things are considered to be language features by many, have been discussed to death by developers and users alike, and are unlikely to be changed or modified any time soon.

Re:Python 2.8 Un-release Schedule by trimbo on Tuesday March 13, 2012 @02:33AM (#3697276)
The unicode change is net-even functionally with 2.x. Unicode everywhere is a nice goal, but let's not pretend that 2.x can't do unicode and that 3.x is the only solution.
Re:Python 2.8 Un-release Schedule by maaku on Tuesday March 13, 2012 @04:53AM (#3697562)
Not to mention that 3.x breaks many things about strings and unicode that were perfectly fine under 2.x. Things like forcing separate codecs for str/unicode (double the work!) and the elimination of basestr (what? why?). Armin did a great article on this a while back.
Re:Python 2.8 Un-release Schedule by dagw on Tuesday March 13, 2012 @04:23AM (#3697495)
Sure python2 can do Unicode, but it's a pain and it's far too easy to introduce bug if you're not paying attention. Unicode everywhere is probably the only python3 feature I miss with any regularity when using python2.