Seriously this article is INCREDIBLY naive. We needed Python 3 to not be backwards compatibility because Python 2 was suffocating the core devs. There were serious innate problems in the language that made it impossible to make the real important changes we need.
And third party lib support? Python 3 has everything except the libraries that need bytestrings and with python 3.5 we have the support we need for them to move forward as well so that argument is ENTIRELY bogus.
DO NOT upvote this article. It's written by someone who doesn't understand the situation, who doesn't care to understand it, and is just whining about some extra sys-admin stuff they have to do as a result of a change that will ultimately make python a much better language than ever before.
There were arguments against Python 3 in the past but seriously learn to read the PEPs. All the real issues are being addressed and all the crap this article mentioned were arguments from 2-3 years ago. Get up to date, educate yourself on what's going on in the language now-a-days. Python 3 has become a hundred times better than Python 2 ever was. Things like async-io, bytes % formatting, etc are moving us forward in the language not back. Python 2 is no longer a modern language and while there's nothing wrong with using it for the next couple years to ease migration efforts IT IS A DEAD LANGUAGE. There are no longer any arguments supporting it, and the community has moved on. You should too.
2
u/fuzz3289 May 26 '14
This article is total bullshit.
Seriously this article is INCREDIBLY naive. We needed Python 3 to not be backwards compatibility because Python 2 was suffocating the core devs. There were serious innate problems in the language that made it impossible to make the real important changes we need.
And third party lib support? Python 3 has everything except the libraries that need bytestrings and with python 3.5 we have the support we need for them to move forward as well so that argument is ENTIRELY bogus.
DO NOT upvote this article. It's written by someone who doesn't understand the situation, who doesn't care to understand it, and is just whining about some extra sys-admin stuff they have to do as a result of a change that will ultimately make python a much better language than ever before.
There were arguments against Python 3 in the past but seriously learn to read the PEPs. All the real issues are being addressed and all the crap this article mentioned were arguments from 2-3 years ago. Get up to date, educate yourself on what's going on in the language now-a-days. Python 3 has become a hundred times better than Python 2 ever was. Things like async-io, bytes % formatting, etc are moving us forward in the language not back. Python 2 is no longer a modern language and while there's nothing wrong with using it for the next couple years to ease migration efforts IT IS A DEAD LANGUAGE. There are no longer any arguments supporting it, and the community has moved on. You should too.