Hi, On Fri, 17 Apr 2015 17:11:45 -0400 (EDT), Geoffrey Thomas wrote: > I've written up the proposal I made a few days ago for a /usr/bin/python > launcher that keeps the API of being Python 2, but lets scripts opt in to > running on Python 3: > > https://ldpreload.com/blog/usr-bin-python-23 > > Let me know if you think this is a good or bad idea: I'll submit this as a > PEP as soon as we have rough consensus that this is a good idea. (We can > bikeshed the details once the idea itself is a draft PEP.)
To be honest, I don't like this proposal.
- Newly written code should *just* use Python 3 (there are exceptions, but
very few).
- If existing code supports Python 3, and its developers consider Python 3
as a target platform, then it should *just* use python3 shebang.
Python 3 appeared seven years ago (at approximately the same time as
Python 2.6, which is the minimal version for most bilingual code), so it
is available almost everywhere. When the proposed PEP is accepted[1] and
adopted by the distributions[2], the probability of *not* having Python 3
will be close to zero.
- Existing code that has not been ported to Python 3 should continue to work
(with Python 2), without any changes to it. These three cases cover most
of the Python code.
[1] which I hope will not happen
[2] the next Debian release is no sooner than in 2017, nine years since the
first Python 3 release
--
Dmitry Shachnev,
who is a bit slow on catching up with his mails.
signature.asc
Description: OpenPGP digital signature
