Is there already a repository for Jessie packages? if so, this could be fixed there, then. Or can it be fixed in Wheezy? it’s a simple symlink, after all.
It’s sad that debian doesn’t follow this PEP: There is no simple way to allow executing ./foobar.py on any system reliably if foobar.py uses python 2: "#!/usr/bin/env python2" won’t work on debian and "#!/usr/bin/python" won’t work on arch. This motivates python developers to violate the PEP as well, too, since debian has more users than archlinux (which *follows* that PEP). Debian essentially says “fuck python hashbangs that work on archlinux, we rather force everyone to write bash wrappers if they want to support every distro”. Those wrappers aren’t trivial, either; I think you have to do the following or something like that: #!/bin/bash python="$((which python2 || which python) | tail -1)" "$python" foobar.py i hope you can understand my frustration with this issue now. 2012/10/2 Scott Kitterman <deb...@kitterman.com>: > On Tuesday, October 02, 2012 06:27:42 PM you wrote: >> 2012/10/2 Scott Kitterman <deb...@kitterman.com>: >> > Developers that jump the gun and start using a feature before it's widely >> > deployed should not be surprised it doesn't work everywhere. Regardless >> > of >> > the severity level we stick on the bug, the release team will review the >> > change and they've already said they won't accept it. >> >> so when can i expect the bug to be fixed? after wheezy is released? >> >> after all, it’s just a simple symlink: no effort necessary, no risk >> introduced. > > Yes. The release team is inundated with "It's just a ..." requests and they > get a uniform answer: No. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
