Author: mtredinnick Date: 2006-07-12 02:40:28 -0500 (Wed, 12 Jul 2006) New Revision: 3336
Modified: django/trunk/docs/settings.txt Log: Made it clear that we do not alter the process environment when manual settings configuration is used. Modified: django/trunk/docs/settings.txt =================================================================== --- django/trunk/docs/settings.txt 2006-07-11 20:38:27 UTC (rev 3335) +++ django/trunk/docs/settings.txt 2006-07-12 07:40:28 UTC (rev 3336) @@ -760,6 +760,13 @@ not necessarily the timezone of the server. For example, one server may serve multiple Django-powered sites, each with a separate time-zone setting. +Normally, Django will set the ``os.environ['TZ']`` variable to the timezone +you specify in this variable. All your views and models will therefore +automatically operate in the correct timezone. However, if you are using the +manual configuration option (see below), the environment variable will not be +touched and it is up to you to ensure your processes are running in the +correct environment. + USE_ETAGS --------- @@ -837,6 +844,15 @@ setting is not passed to ``configure()`` and is needed at some later point, Django will use the default setting value. +Configuring Django in this fashion is mostly necessary -- and, indeed, +recommended -- when you are using a piece of the Django framework inside a +larger application. Consequently, when configured via +``settings.configure()``, Django will not make any modifications to the +process environment (see the explanation of ``TIME_ZONE``, above, for why this +would normally occur). It is assumed that you are already in full control of +your environment in these cases and have configured your environment as +required in some other fashion. + Custom default settings ----------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates -~----------~----~----~----~------~----~------~--~---
