On Jan 7, 4:42 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Putting that in settings.py is too late, since by the thing that reads > settings.py is Django itself, so it's already been imported. You have to > modify your Python import path *before* anything Django-related is > imported.
He's right. We keep our djangos in by-date-downloaded directories. Here is a snip from our production site: PythonPath "['/var/www/production', '/usr/local/django/django-111707'] + sys.path" django-111707 contains one file, the django directory from the svn checkout. When we need to roll to a new django release, we put it in its own directory, configure our development and staging servers to work with it, and on release, we make the appropriate change in the production server's PythonPath. This process saved our ass when we rolled to a new version about 2 days after the AutoEscape feature went in and I hadn't read the Backward Incompatible Changes page (See http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges). We are getting ready to move to trunk/7001 (to incorporate a patch made by Malcolm. Thanks, Malcolm!), but it first gets beaten up in the back room before it's allowed to go primetime. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
