Yes, I understand. I've worked in corporate America for a couple of decades. Anyway, I got downvoted for my comment so I'll leave it up to the community to figure out how to deprecate 2.x.
Hey, I get what you are saying. It's up to the developers to move to Python 3. I am just trying to say that there's a difference between a "make sure every bit of library code you write works in Python 3 first, then backport to Python 2 if necessary" and "every project must convert to Python 3 now". I am all for the former. If you write a library, write it in 3, then see if the unit tests pass in 2.
Comments
Yes, I understand. I've worked in corporate America for a couple of decades. Anyway, I got downvoted for my comment so I'll leave it up to the community to figure out how to deprecate 2.x.
Hey, I get what you are saying. It's up to the developers to move to Python 3. I am just trying to say that there's a difference between a "make sure every bit of library code you write works in Python 3 first, then backport to Python 2 if necessary" and "every project must convert to Python 3 now". I am all for the former. If you write a library, write it in 3, then see if the unit tests pass in 2.