3👍
If you’re using windows, you’ll need to put your project’s directory (the one with manage.py
in it) into an environment variable called PYTHONPATH
.
0👍
Since this is highly ranked on Google and I got here while searching for an answer I’ll share my solution:
I have a project built on my machine, packaged into a debian package and installed on a test machine. On my machine I use the runserver but on the testmachine I use apache (which was using fine). When changing database from sqlite to postgresql I could not do shell or syncdb etc (all manage commands). The problem here was that manage.py was owned by www-data and it had to be root for these commands to work…
sudo chown root. manage.py
- [Django]-Django installing multiple apps on the same page
- [Django]-How to send password reset mail from custom Django views?
- [Django]-Django server not running on host with vagrant
0👍
Another different answer 😉 I’m walking the “Django for the Impatient: Building a Blog” chapter from “Python Web Development with Django” and it suggests creating a “dotted” module so I registered my application as “x.y” which it didn’t like. Changing to “y” which matched the file-system as:
/x
+ manage.py
+ /x
+ settings.py
+ /y
+ models.py
Worked for me.