[arch-general] python 2.7.1-3 -> python 2.7.1-4 broke django
Hello Fellow Archers, With the last update, I'm not able to run ./manage.py at all which I was just before the update. (I can't downgrade because I wiped pacman cache) Here is what it says: $ ./manage.py runserver 192.168.56.101:8000 bash: ./manage.py: /usr/bin/python2^M: bad interpreter: No such file or directory $ /usr/bin/python2 Python 2.7.1 (r271:86832, Jan 6 2011, 11:51:37) [GCC 4.5.2] on linux2 Type "help", "copyright", "credits" or "license" for more information.
$ /usr/bin/env python2 Python 2.7.1 (r271:86832, Jan 6 2011, 11:51:37) [GCC 4.5.2] on linux2 Type "help", "copyright", "credits" or "license" for more information.
$ y -Qs python2 extra/python2 2.7.1-4 A high-level scripting language extra/python2-distribute 0.6.14-2 A collection of extensions to the Python 2 distutils Any ideas? --- Quis custodiet ipsos custodes?
On 11 January 2011 01:18, Alper KANAT
$ ./manage.py runserver 192.168.56.101:8000 bash: ./manage.py: /usr/bin/python2^M: bad interpreter: No such file or directory
Any ideas?
It looks like the shebang is incorrect at the start of the manage.py script, it's got a carriage return (the ^M) so it can't find /usr/bin/python2 because as far as it's concerned the executable doesn't exist, see if removing that helps.
participants (2)
-
Alper KANAT
-
Damien Churchill