Important change: flatpages and redirects refactored into standalone/optional apps
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 flatpages and redirects into standalone, optional apps" section of the backwards-incompatible changes page: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges This change makes Django leaner and meaner: It cuts a bit of functionality that Django did by default but not everybody wanted to take advantage of. If you *do* want to use flatpages and redirects, check out these two new pieces of documentation: * The flatpages app: http://www.djangoproject.com/documentation/flatpages/ * The redirects app: http://www.djangoproject.com/documentation/redirects/ Please respond to this thread if you have any questions! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
Re: django-admin not seeing settings.py
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. 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 hadn't > > exported those values or sourced the file? > > > 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 python 2.3) For my interactive sessions, I run the following commands (I actually have them in a file devel.py, and I cd to the folder containing devel.py, and do "import devel" from within a python session): import sys import os sys.path = sys.path + ['/path/to/my/app/','/path/to/django/src/'] os.environ['DJANGO_SETTINGS_MODULE'] = 'myapp.settings' Alternatively, to set it permanently, put the export PYTHONPATH and DJANGO_SETTINGS_MODULE settings in your ~/.bashrc, then start a new bash session. Luke Luke -- "I washed a sock. Then I put it in the dryer. When I took it out, it was gone." (Steven Wright) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/
Re: django-admin not seeing settings.py
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 python 2.3) At a command line, type 'echo $PYTHONPATH' and hit Enter. -- "May the forces of evil become confused on the way to your house." -- George Carlin
Re: django-admin not seeing settings.py
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 file to > set your DJANGO_SETTINGS_MODULE and PYTHONPATH, and then hadn't > exported those values or sourced the file? > 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 python 2.3) -- Waylan Limberg [EMAIL PROTECTED]
Re: django-admin not seeing settings.py
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 file to > set your DJANGO_SETTINGS_MODULE and PYTHONPATH, and then hadn't > exported those values or sourced the file? > > > -- > "May the forces of evil become confused on the way to your house." > -- George Carlin > -- Waylan Limberg [EMAIL PROTECTED]
Re: django-admin not seeing settings.py
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 hadn't exported those values or sourced the file? -- "May the forces of evil become confused on the way to your house." -- George Carlin
Re: django-admin not seeing settings.py
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
[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 need to keep the original project running and I want to install the > new admin branch to create a new project. But I need to do it on the > same server. Is it possible to run the two side by side? What is the > best way of doing this? > > I'm a bit scared of breaking my original project (being paranoid > perhaps) > > Thanks > Charlotte > > You can do this by checking out new-admin to a different location, and then using a different PYTHONPATH setting in your server setup. Rob
Re: django-admin not seeing settings.py
> 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 django/conf/global_settings.py). > > > > That's what I suspected. Same situation for me. I specify mysql, but it complains of postgresql problems. Its not finding the settings file. > > > Make sure your "myproject" directory is on the PYTHONPATH. You should > > > be able to switch to another, unrelated directory -- such as "/temp/" > > > -- start the Python interactive interpreter and type "import > > > myproject.settings". I tried this through the interpreter, same results as Waylan. I'm new to python, but I wouldn't expect a python environment variable to remain persistent across interpreter sessions. Are they really supposed to ? If so, how long would they persist ? Tried django-admin.py init --pythonpath=/Users/me/Sites/djangotest --settings=myproject.settings Didn't work. This is maybe a problem in django-admin ? I tried setting the unix envir variable PYTHONPATH Still doesn't find it. thanks all.
