On Tue, 15 Jan 2008, Brett Parker wrote:
> On 14 Jan 18:37, Raphael Hertzog wrote:
> > On Mon, 14 Jan 2008, Filippo Giunchedi wrote:
> > > Would it be necessary to know if django-admin is called by the standard
> > > interpreter? Anyway, how about something like this?
> >
> > Well, in fact using sys.executable seems to be enough:
> > $ cat test.py
> > #!/usr/bin/env python
> >
> > import sys
> >
> > print sys.executable
> >
> > $ ./test.py
> > /usr/bin/python
> > $ python2.5 ./test.py
> > /usr/bin/python2.5
> > $ python2.4 ./test.py
> > /usr/bin/python2.4
> >
> > So django-admin should update the shebang of manage.py with the value of
> > sys.executable.
>
> We previously had a patched django-admin that did this, and went back to
> putting the shebang to the default python...
And the reasoning was?
As long as the patched django-admin puts /usr/bin/python when directly
called ("django-admin") or when called with "python /usr/bin/djando-admin"
I don't see any problem in doing the change. It's no-op for the standard
use and enable a supplementary usage to force an alternative python
version.
> I'd rather it was left as using the default python, and if people want
> to use a non default one they either edit the files or run it using the
> other python. Open to suggestion though.
If that's a decision, please tag the bug "wontfix" at least.
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
