On Jul 24, 2013, at 02:14 PM, Scott Kitterman wrote: >Don't we have more important things to worry about? It only matters at all if >one is contemplating switching the /usr/bin/python symlink to python3. We >aren't, so let's not change something just to change it.
If it ain't broke, don't fix it, eh? :) I think it's low risk, and probably an easy change, but I agree that *right now* it's probably low value. Maybe a useful way to think about it is in the context of future Debian releases. Let's say that in May 2015, we decide the tide has turned enough to begin recommending Python 3 and "deprecating" Python 2. If PEP 394 changes its recommendation then, what can we do now to prepare for a smoother transition in a future Debian release? Maybe jessie will be out by then, but what about jessie+1? Will changing the shebang lines now make life easier for us in 2 years? Do you ever foresee a time when /usr/bin/python gives you Python 3 on Debian? >When does security support for python2.7 end? Generally, security releases are made for 3 years after the last binary/maintenance release. E.g. 3.1.4 was the last maintenance release on June 11, 2014 and PEP 375[*] says the last security release will be in June 2014. So, if form holds, Python 2.7 will drop all upstream support in May 2018. It wouldn't surprise me if that guarantee was made longer, but I wouldn't expect to see more than a release a year at that point. -Barry [*] http://www.python.org/dev/peps/pep-0375/ The Python 3.1 release schedule -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130724150053.01d66324@anarchist
