#2315: [patch] Timezone bug in development server using a Windows environment
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: django-admin.py
runserver
Version: SVN | Resolution:
Keywords: timezone datetime | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by mtredinnick):
One question before I commit this: how sensitive is the solution to where
the "import time" statement is? I would like to have it just before or
just after "import os" in order to keep things in a logical order (system
imports all together).
I have no problem with referencing a bug in the docs, by the way. The bug
report doesn't contain crucial information -- just backup supporting
evidence. So I'll leave that reference there; you can still read the docs
and make sense of them without referring to the bug report.
--
Ticket URL: <http://code.djangoproject.com/ticket/2315#comment:18>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
