* Neil Schemenauer <[EMAIL PROTECTED]> [011022 17:47]: > Anthony Towns wrote: > > On Mon, Oct 22, 2001 at 10:13:17AM +0200, Gregor Hoffleit wrote: > > > Say, you would install 2.1.2 in /usr/local. > > > > How about we just say "Don't install other versions of python in > > /usr/local" ? > > Please no. Making this work properly is not hard. Besides, if the > magic is "#!/usr/bin/env python" then we would have to say "don't > install other versions of python in your path".
Exactly. IMHO this is a no-go, we should not restrict our users in that way. Furthermore, would there be any reason at all for using "#!/usr/bin/env" in Debian scripts ? I don't see any. Btw, cf. the discussion thread on python-dev that I started by asking that kind of question. The tendency was that in general every Python application is guaranteed to work only on a specific Python version. Mailman 2.0 only runs on Python 1.5.2. Mailman 2.1 runs on Python 2.0. Zope 2.2 runs on Python 1.5.2. Zope 2.4 runs on Python 2.1. Every other combination is just a lucky coincidency (cf. the python-dev archives at http://mail.python.org/pipermail/python-dev/ for the full discussion). I don't see any reason why we should actively work towards enabling a user to override the intended version, with the potential damage of breaking scripts. If the maintainer of a script is really aware of a legitimate reason for doing this, he is welcome to use /usr/bin/env. Gregor
