I'm very familiar with it.
Kerrick Staley <kerrick@kerrickstaley.com> wrote:
>Thanks!
>
>The upstream recommendation (from PEP 394 [1]) is that, going forward,
>portable scripts *can't* assume python is python2, and *should* use
>python2.
>
>- Kerrick
>
>[1] http://www.python.org/dev/peps/pep-0394/
Now we get to Arch is insane.
They've put developers in a difficult spot. They have to choose between /usr/bin/python2 and works on Arch and some newer releases and /usr/bin/python and works everywhere except Arch.
The only suggestion I can make is that it's generally not that hard for new code to make it work for both python2.7 and python3.3. Then there's no need to care.
Archive: [🔎] 7a1743e6-afc6-44f0-9f29-5d5a60af2cb6@email.android.com" target="_blank">http://lists.debian.org/[🔎] 7a1743e6-afc6-44f0-9f29-5d5a60af2cb6@email.android.com
Scott K
--
To UNSUBSCRIBE, email to debian-python-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org