Re: sys.path trickery in settings.py

Rob Hudson wrote: > I wouldn't say it's frowned upon, per se, but you're making things > hard for yourself. Why not add Django to your Python path? > > There are other ways to go, too... > I use buildout, which lets me specifiy which eggs I want to use for each project, extra svn checkouts, s

Re: sys.path trickery in settings.py

I wouldn't say it's frowned upon, per se, but you're making things hard for yourself. Why not add Django to your Python path? There are other ways to go, too... In the shell you're working in: $ export PYTHONPATH=~/pkg/django-trunk Then ./manage.py will find it without editing the file. For my

sys.path trickery in settings.py

Hi, I keep my django-trunk installation (and other things like django_evolution) in my home directory, outside the system-wide installation To avoid having to set PYTHONPATH in the environment, I set do this in my project settings.py file: # sys.path trickery -