#2315: [patch] Timezone bug in development server using a Windows environment
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: django-admin.py
runserver
Version: SVN | Resolution: fixed
Keywords: timezone datetime | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by Marc Fargas <[EMAIL PROTECTED]>):
Replying to [comment:24 mtredinnick]:
> Replying to [comment:22 Marc Fargas <[EMAIL PROTECTED]>]:
> > Replying to [comment:20 SmileyChris]:
> > > I tested the new patch, still works fine.
> >
> > SmileyChris, mtredinnick asked whether the "import time" statement
'''must''' be where it is or if it can be placed just above/below the
import os line, can you check if the import statement can be moved?
>
> Just to clarify, Chris posted a new patch (the one he tested) with the
import statement moved to a better place. All is good.
Sorry, didn't spot the new upload ;)
--
Ticket URL: <http://code.djangoproject.com/ticket/2315#comment:26>
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
-~----------~----~----~----~------~----~------~--~---
