On Dec 10, 2007 3:03 PM, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > Hmm. What you said about not having Django installed in site-packages > makes me think... > > What does your PYTHONPATH environment variable have in it? >
I wasn't setting PYTHONPATH to anything. Normally packages are picked up just fine when they're in the current directory. I put Django there because I would rather not add pre-release software to site-packages. I had a hunch that having Django in the current directory was the problem, and now that seems to be confirmed. Here are some more trials: - Django in site-packages only: works - Django in site-packages and in $PWD: fails - Django in $SOMEDIR and PYTHONPATH=$SOMEDIR: works - Django in $SOMEDIR and in $PWD, and PYTHONPATH=$SOMEDIR: fails - Django in $PWD only: fails - Django in $PWD and PYTHONPATH=$PWD: fails Any of the failure cases will work if I add '--settings=mysite.settings' to the command line, or if I use a revision that doesn't have your 6718 change. Do you possibly have the current directory listed before the path to > Django? Because if you try to > > from django.conf import settings > > before your settings module has been identified, weird things might > happen. (I don't know what exactly...I'm grasping at straws at the > moment.) > It does look like the settings object that I get in urls.py has only the default settings and none of the local settings. But I don't know how 6718 changed this behavior, or why adding --settings fixes it. Josh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
