Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-05-15 Thread Raphael Hertzog
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

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Andrea Gasparini
Package: python-django Version: 0.96.1-1 Django-admin should use the right python interpreter used to call the script when he creates manage.py. [EMAIL PROTECTED]:temp$ python2.4 /usr/bin/django-admin startproject foo [EMAIL PROTECTED]:temp$ head -n2 foo/manage.py #!/usr/bin/env python from

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Andrea Gasparini
Verified that it appear also in ubuntu. So, I reported this bug also in Launchpad: https://bugs.edge.launchpad.net/debian/+source/python-django/+bug/182807 -- -gaspa- --- https://launchpad.net/~gaspa - -- HomePage:

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Raphael Hertzog
severity 460662 wishlist retitle 460662 django-admin should hardcode the path of the python interpreter if it's not the same as tthe standard /usr/bin/python thanks On Mon, 14 Jan 2008, Andrea Gasparini wrote: Package: python-django Version: 0.96.1-1 Django-admin should use the right python

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Andrea Gasparini
This is at best a wishlist report : Yes, it would be so, i missed the tag, sorry. 1/ since django-admin is in /usr/bin/ it's meant to be directly called (without any explicit interpreter) It could be done to rely on a specific version of python, or because, as you said below, i changed

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Raphael Hertzog
On Mon, 14 Jan 2008, Andrea Gasparini wrote: I know that this is Debian, and you go against _debian_ bugs. But I guess that you could mainly support django for 2.4 python version, and why don't try to 'partially' support also other versions? At least we could minimize diversion between

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Filippo Giunchedi
Hi, On Mon, Jan 14, 2008 at 04:08:57PM +0100, Raphael Hertzog wrote: On Mon, 14 Jan 2008, Andrea Gasparini wrote: I know that this is Debian, and you go against _debian_ bugs. But I guess that you could mainly support django for 2.4 python version, and why don't try to 'partially' support

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Raphael Hertzog
On Mon, 14 Jan 2008, Filippo Giunchedi wrote: It's not automatic since you have to change the invocation of django-admin to give a special interpreter. :) And if you're doing something explicit like that you might as well just edit the generated file. Indeed, thinking about this I am

Bug#460662: django-admin doesn't create manage.py with the right python interpreter

2008-01-14 Thread Brett Parker
On 14 Jan 18:37, Raphael Hertzog wrote: On Mon, 14 Jan 2008, Filippo Giunchedi wrote: It's not automatic since you have to change the invocation of django-admin to give a special interpreter. :) And if you're doing something explicit like that you might as well just edit the