Given the large gap between python 2 and python 3 (and the fact that
python 3 scripts generally don't run on python 2), a lot of script
writers are beginning to use python2 references in their scripts.
aka:
#/usr/bin/env python2
and
#/usr/bin/env python3
I've tested this on every other current release out there (Arch,
Ubuntu, SUSE, SLES, RedHat Linux Enterprise, Fedora) and python2 exists.
This is going to put Debian at a disadvantage as all of these scripts
starting to use python2 interpreters will fail unless the end user
symlinks python2 -> python2.7 (having python2.7 is less predictable
across platforms)
I agree this isn't critical, but it will have quite a user impact.
-- Alex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
