Important change: flatpages and redirects refactored into standalone/optional apps

2005-11-10 Thread Adrian Holovaty
All, As of a code update today, flatpages and redirects, two features that have been installed with Django by default but had not been documented, are now optional add-ons. This is a backwards-incompatible change, so all Django users are advised to follow the instructions in the "Separated

Re: django-admin not seeing settings.py

2005-11-10 Thread Luke Plant
On Thu, 10 Nov 2005 12:16:47 -0500 Waylan Limberg wrote: > > On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote: > > > > On 11/10/05, felix <[EMAIL PROTECTED]> wrote: > > > do this: > > > export DJANGO_SETTINGS_MODULE=myproject.settings > > > > Yeah, that's mentioned in the documentation.

Re: django-admin not seeing settings.py

2005-11-10 Thread James Bennett
On 11/10/05, Waylan Limberg <[EMAIL PROTECTED]> wrote: > I still don't have it working for me, and I did the export > DJANGO_SETTINGS_MODULE=myproject.settings thing. Whats the best way to > see what your PYTHONPATH is set to and change it? Maybe something is > wrong there. (I'm on Debian with

Re: django-admin not seeing settings.py

2005-11-10 Thread Waylan Limberg
On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote: > > On 11/10/05, felix <[EMAIL PROTECTED]> wrote: > > do this: > > export DJANGO_SETTINGS_MODULE=myproject.settings > > Yeah, that's mentioned in the documentation. Perhaps what was > happening was that you'd changed a .bash_profile or .bashrc

Re: django-admin not seeing settings.py

2005-11-10 Thread Waylan Limberg
On 11/10/05, James Bennett <[EMAIL PROTECTED]> wrote: > > On 11/10/05, felix <[EMAIL PROTECTED]> wrote: > > do this: > > export DJANGO_SETTINGS_MODULE=myproject.settings > > Yeah, that's mentioned in the documentation. Perhaps what was > happening was that you'd changed a .bash_profile or .bashrc

Re: django-admin not seeing settings.py

2005-11-10 Thread James Bennett
On 11/10/05, felix <[EMAIL PROTECTED]> wrote: > do this: > export DJANGO_SETTINGS_MODULE=myproject.settings Yeah, that's mentioned in the documentation. Perhaps what was happening was that you'd changed a .bash_profile or .bashrc file to set your DJANGO_SETTINGS_MODULE and PYTHONPATH, and then

Re: django-admin not seeing settings.py

2005-11-10 Thread felix
ok mine is working now. do this: export DJANGO_SETTINGS_MODULE=myproject.settings and thereafter all the django-admin.py commands work correctly.

Re: Running new-admin branch with trunk

2005-11-10 Thread Robert Wittams
[EMAIL PROTECTED] wrote: > Hi > > I currently have the trunk django running a little prject on my server > (it's working well its a great product) > > However when I come to make a second application some of the things I > need to do I'm told are only possible in the new admin branch. > > I

Re: django-admin not seeing settings.py

2005-11-10 Thread felix
> On 11/7/05, Waylan Limberg <[EMAIL PROTECTED]> wrote: > > On 11/7/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > > Django isn't finding your settings.py file. It's falling back to > > > "postgresql" because that's the default fallback (according to the > > > file