Re: "ImportError: No module named django" with MacPorts

2010-03-03 Thread Tim Jones
Sorry, I should clarify. When I wrote: > So I tried specifying the site-packages path at the top of my script... I meant that I added these lines: ~~ import sys sys.path.insert(0, "/opt/local/lib/python2.5/site-packages") ~~ =T= -- You received this message because you are subscribed to the

Re: "ImportError: No module named django" with MacPorts

2010-03-03 Thread Tim Jones
in a few different ways: > > python django-admin.py startproject fake_project_name > django-admin.py startproject fake_project_name > /explicit/path/to/some/python/installation/python django-admin.py > startproject fake_project_name > > Let us know what you get. > > Shawn

Re: "ImportError: No module named django" with MacPorts

2010-03-03 Thread Tim Jones
Thanks for the reply. "which python" returns: /opt/local/bin/python "python -V" returns: Python 2.5.5 I know I've got the OSX default Pythons installed as well, but I've done my best to avoid running those. Like I said in my first email, printing sys.path in the python prompt returns a big