5 ms·
What's wrong with Python 2.7? (real question, not flamebait)
by bduerst 9y ago
What's wrong with Python 2.7? (real question, not flamebait)
- minimaxir 9y agoSee similar thread made yesterday: https://news.ycombinator.com/item?id=15647727 https://news.ycombinator.com/item?id=15647727
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- bduerst 9y agoThat didn't say anything about what's wrong with 2.7
- neves 9y agoPython 2.7 is frozen. It just get security updates. The community is investing in Python 3. All the main numerical libraries are already compatible with Python 3 and, unless you need a very specific library, there is no reason to start developing new projects in Python 2 nowadays.
- nerdponx 9y agoUnicode text handling.
- yarrel 9y agoThis is wrong with Python 3 as well in real world use.
- nerdponx 9y agoHow so?
- danso 9y agoMaybe the parent commenter is referring to issues brought up by Armin Ronacher (among others): http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ Don't know what has changed since 2014. My perception is that Armin feels he's been pigeonholed as being more anti-Py3 than he actually is, at least with the state of Python in 2016: http://lucumr.pocoo.org/2016/11/5/be-careful-about-what-you-dislike/ http://lucumr.pocoo.org/2016/11/5/be-careful-about-what-you-... > In fact, I myself campaigned for some changes to Python 3 that made it possible to achieve better ports (like the reintroduction of the u prefix on Unicode string literals) and the bulk of my libraries work on Python 3 for many years now. It's a fact that in 2016 the problems that people have with Python 3 are different than they used to have before.