[Toshio Kuratomi, 2011-03-03]
On Thu, Mar 03, 2011 at 09:55:25AM +0100, Piotr Ożarowski wrote:
If /usr/bin/python will be disallowed in shebangs on the other hand (and all scripts will use /usr/bin/python2, /usr/bin/python3, /usr/bin/python4 or /usr/bin/python2.6 etc.) I don't see a problem with letting administrators choose /usr/bin/python (right now not only changing it from python2.X to python3.X will break the system but also changing it from /usr/bin/python2.X to /usr/bin/python2.Y will break it, and believe me, I know what I'm talking about (one of the guys at work did something like this once))
[all IMHO, dunno if other Debian's python-defaults maintainers agree with me]
Thinking outside of the box, I can think of something that would satisfy your requirements but I don't know how appropriate it is for upstream python to ship with. Stop shipping /usr/bin/python. Ship "python" in an alternate location
to be honest, I didn't want to be so radical, a clear policy (PEP?) would be enough for me - we'd then replace all /usr/bin/python shebangs with /usr/bin/python2 at build time (with a warning to report bug upstream) and forward all complainers to this PEP) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645