Python Software Foundation survey finds that a significant number of Python developers are still using Python 2 for data analysis, computer graphics, and devops.
I don’t see a problem. For one, it’s been 15 years: the vast majority of libraries have been ported by now. And like you said, you can fix the syntax with basically a find/replace script, so any stragglers can be modified easily.
There really isn’t any excuse to still be using Python 2 anymore
While I agree that people should have moved on for a while, the idea that porting Python 2 to 3 only involves “find and replace” or a tool like 2to3 is only true in the most trivial cases. Anything that touches bytes, unicode, network or files to do anything remotely involved needs a lot more care. I should know, our codebase still suffers from the occasional bug due to this, even though it’s been years.
I don’t see a problem. For one, it’s been 15 years: the vast majority of libraries have been ported by now. And like you said, you can fix the syntax with basically a find/replace script, so any stragglers can be modified easily.
There really isn’t any excuse to still be using Python 2 anymore
While I agree that people should have moved on for a while, the idea that porting Python 2 to 3 only involves “find and replace” or a tool like 2to3 is only true in the most trivial cases. Anything that touches bytes, unicode, network or files to do anything remotely involved needs a lot more care. I should know, our codebase still suffers from the occasional bug due to this, even though it’s been years.