The way 2.x -> 3.x was handled is/was/will is an absolute disaster. Upgrading simple scripts is a non-issue. Larger projects seem to always be a horrible pain.
The way 2.x -> 3.x was handled is/was/will is an absolute disaster. Upgrading simple scripts is a non-issue. Larger projects seem to always be a horrible pain.
I've upgraded projects, but this "you refuse to upgrade" business bothers me. There is a reason people haven't: The way Python handled all of this is horrid.
It's often easier to just move to another language.
By count of lines, 0.04% of Python code I've published exists only to deal with 2 vs. 3 issues. Of that code, 34% consists of importing and applying a decorator from Django that handles setting up either __str__() or __unicode__() on a Django model as appropriate. Tellingly, there are exactly two lines I could find that aren't that decorator and which deal with a str/unicode issue.
And that's in code which doesn't just run on Python 3, it supports 2 and 3 in the same codebase.
It actually become usable somewhere around 3.2/3.3, released in 2011/2012.
- 2008-2012: Becoming actually usable.
- 2012-2016: Libraries porting over
- 2016-2020: Applications porting over (more work needs to be done here. See http://portingdb.xyz )
Things I still have in Python 2.7:
- Code that runs on low-end shared hosting. There's a Python 3, but it's 3.2, the least-compatible version. No "six", and "u'xyz' isn't allowed.
- ROS, the Robot Operating System. Python 3 support is coming, but it's not really here yet.
I converted over the dedicated servers and some IoT stuff a year ago.
The types stuff probably should have been called Python 4, not Python 3.6. Those are major language changes. The optional-types-that-are-not-checked thing seems a bad idea. I can see having checked types; that allows some important optimizations. When you know something is a machine type, such as an int or float, you don't have to box it. But the feature of type declarations without checking is a foot gun.
*van Rossum
I wouldn't say that's an accurate statement of what Guido does every day :)
(nb: I work at Dropbox, and have worked with Guido at Dropbox.)
[1] https://www.quora.com/What-version-of-Python-does-Dropbox-us...
From https://gvanrossum.github.io/ :
But when my last name is used alone to refer to me, it is capitalized, for example: "As usual, Van Rossum was right."