4 ms·
You've only got 2 years, get started now! If you need to do it gradually (as would be wise for a gigantic codebase), start using `six` to make your codebase for
by theptip 9y ago
You've only got 2 years, get started now! If you need to do it gradually (as would be wise for a gigantic codebase), start using `six` to make your codebase forwards-compatible. Then when all your tests pass on python3, cut over, and remove `six`.
(Or take a gamble on Google taking over support for Python2 when it officially goes EOL, I suppose).
- sigjuice 9y agoRedhat (or someone like them) might keep the lights on for Python 2 if a large enough customer leans on them.
- kstrauser 9y agoThere's approximately zero chance that RedHat will support backports of huge, many-contributor projects like NumPy or Django that are dropping Python 2 support (see: https://docs.scipy.org/doc/numpy/neps/dropping-python2.7-proposal.html https://docs.scipy.org/doc/numpy/neps/dropping-python2.7-pro... and https://docs.djangoproject.com/en/2.0/releases/2.0/ https://docs.djangoproject.com/en/2.0/releases/2.0/). They just can't - there aren't enough hours in the day. Five years from how, you don't want to be explaining to your CEO why it's literally impossible for you to integrate with a third party SDK because your stack is so ancient and petrified that new code can't incorporate it.