django-admin.py not added to path

[Carl Karsten]

Binary package hint: python-django

http://www.djangoproject.com/documentation/install/ says to add django-admin.py to path, so the package should too.

"""
On Unix-like systems, create a symbolic link to the file django-trunk/django/bin/django-admin.py in a directory on your system path, such as /usr/local/bin. For example:
ln -s `pwd`/django-trunk/django/bin/django-admin.py /usr/local/bin
"""

juser@cp333:~$ locate django-admin.py
/usr/share/python-support/python-django/django/bin/django-admin.py
/var/lib/python-support/python2.5/django/bin/django-admin.py
/var/lib/python-support/python2.5/django/bin/django-admin.pyc

juser@cp333:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

I am not sure why this is here:
juser@cp333:/var/lib/python-support/python2.5/django/bin$ ls -l django-admin.py
django-admin.py -> /usr/share/python-support/python-django/django/bin/django-admin.py

[Andrea Gasparini (gaspa)]

What version are you talking about?

at least from 0.96.1 there's a /usr/bin/django-admin, that is either executable and in PATH.

[Andrea Gasparini (gaspa)]

after some time this bug has still no responses.
I checked feisty, gutsy and hardy packages and as far as I see there's a /usr/bin/django-admin file.
Reopen the bug if you feel there's something wrong.

[Carl Karsten (carlfk)]

ah. I see what happened.

why is it django-admin and not django-admin.py?

All of the django docs refer to it as django-admin.py. I think one of these should happen:
1. add django-admin.py to the .deb install
2. add an issue to django's tracker asking to note that it may only be django-admin.

I have a few bash scrips that all reference django-admin.py so I would want #1.

[Andrea Gasparini (gaspa)]

It's renamed because of the Debian Policy, in http://www.debian.org/doc/debian-policy/ch-files.html#s10.4 it tells:

"When scripts are installed into a directory in the system PATH, the script name should NOT include an extension such as .sh or .pl that denotes the scripting language currently used to implement it."

So, #1 could not be done. you could report this in the upstream django tracker, but i'm not sure that they want to fix it.

About your scripts, i think that you should control the existence of both files and make a choice.