Re: Python PATH question

> > The runserver stuff is a bit too magic. It puts 'root' on sys.path but > > only long enough to import 'mysite' package root. um, i have never experienced this behavior. plug: http://www.wtflab.com/tech/2008/jul/01/developed-directory-structure/ --~--~-~--~~~---

Re: Python PATH question

After reading the documentation, it seems to me that it assumes that root is on the path. I am therefore a little surprised that runserver is not working that way. Maybe it is good to modify manage.py to include root on path so that later migration to mod_python will not cause so many problems. W

Re: Python PATH question

On Jul 14, 11:42 am, Rickard <[EMAIL PROTECTED]> wrote: > Hi, > > The documentation says "The value you use for PythonPath should > include the parent directories of all the modules you are going to > import in your application." > > If I have a typical Django project structure: > > root > - mysit

Python PATH question

Hi, The documentation says "The value you use for PythonPath should include the parent directories of all the modules you are going to import in your application." If I have a typical Django project structure: root - mysite -- myapp1 -- myapp2 I should put root on the Python PATH, right? But