On 7/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:

Anybody have thoughts about this?

Thinking about it further, I am more and more inclined to go with option
#2: don't mess with the environment when running Django components
embedded in another application. But I may be insane (the phrase has
certainly been used in my presence before. :-( ).

Well... if the shoe fits... :-)

Seriously - I'm inclined to agree with #2 as well. In a pure Django app, we know what needs to be/doesn't need to be in the environment. If you are using manual settings, all bets are off in that regard. Document the need for TZ if manually configuring, and leave things the way they are.

Truth be told, I'm even uncomfortable with the way Django sets TZ when settings are loaded. To me, TZ should be documented as an external environment requirement, rather than being a Django setting that affects the environment. At the very least, Django should check if there is an existing TZ setting before overriding it.

Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" 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-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to