Invalid Python shebang in manage.py

[GoogleCodeExporter]

manage.py is a python2 script. As such the shebang should be '/usr/bin/python2' 
and not '/usr/bin/python' which could be python3 or any other python version.

Original issue reported on code.google.com by girard.cedric on 23 May 2011 at 9:27

[GoogleCodeExporter]

That depends on the OS you're using. On Ubuntu 11.04 for example, there is no 
"python2" executable, only "python" and "python2.7".

The "manage.py" script was generated by Django, we didn't modify anything in it.

I don't have any solution for the moment, you need to modify the script 
depending on your operating system ; sorry.

The problem could be fixed when Omoma will be packaged, in package-specific 
fixes.

Original comment by sebast...@tiramiseb.fr on 23 May 2011 at 9:35

• Changed state: WontFix

[GoogleCodeExporter]

There was a python2 in Ubuntu 10.04. And there should be one in 11.04. If not 
this is an Ubuntu bug.
And what about /usr/bin/env python2 ?

I'm sorry but /usr/bin/python does not make any sense to me.

Original comment by girard.cedric on 23 May 2011 at 9:57

[GoogleCodeExporter]

I'll check that more precisely later. Re-opening the issue.

Original comment by sebast...@tiramiseb.fr on 23 May 2011 at 9:58

• Changed state: New

[GoogleCodeExporter]

There was a "python2" file in Ubuntu 10.04 Lucid, but this file is not present 
on Ubuntu 10.10 Maverick, on Ubuntu 11.04 Lenny or on Debian 5.0 Lenny.

The "python2" file is specified in PEP 394, which is still a draft.
http://www.python.org/dev/peps/pep-0394/

I prefer sticking to current usage (apart from bleeding-edge distros like Arch 
Linux ;-) ), and Omoma will obviously switch to the "python2" command when the 
PEP will be finalized and when the command will be officially supported in 
mainstream distributions.

Feel free to make new comments :-)

Original comment by sebast...@tiramiseb.fr on 24 May 2011 at 8:04

• Changed state: WontFix