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 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 django.core.management import execute_manager > [EMAIL PROTECTED]:temp$ /usr/bin/env python > Python 2.5.1 (r251:54863, Oct 5 2007, 13:36:32) This is at best a wishlist report : 1/ since django-admin is in /usr/bin/ it's meant to be directly called (without any explicit interpreter) 2/ django is supported for the current python version mainly (current being defined as the version corresponding to the /usr/bin/python provided by the official "python" package) 3/ your machine is not a "standard" Debian machine since you manually changed the /usr/bin/python symlink to point to python2.5 Why can't you simply edit the manage.py script to match the python version that you'd like to use instead of requiring the script to hardcode any python version that might be currently used? Furthermore, if manage.py hardcodes a python version, the end-result might be that the Django application stops working when the given python version is dropped from Debian while using #!/usr/bin/python makes it work whatever the current version is. I'd let the the bug open some time to let other people comment if they wish, but in the end I think that this request is not reasonable and the bug should thus be closed. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
