#17463: timezones tests fail on Windows
---------------------------------+-------------------------------------
Reporter: kmtracey | Owner: aaugustin
Type: Bug | Status: new
Component: Core (Other) | Version: SVN
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Changes (by aaugustin):
* owner: nobody => aaugustin
* stage: Unreviewed => Accepted
Comment:
So the problem boils down to:
- testing with `settings.TIME_ZONE` == system time zone is deceptive —
some tests can pass by pure luck. That's one reason why I chose EAT, an
uncommon timezone, the other reason being that it doesn't have DST.
- Windows doesn't support `settings.TIME_ZONE` != system time zone.
As explained [http://regebro.wordpress.com/2008/05/10/python-and-time-
zones-part-2-the-beast-returns/ here], not only are the names of timezones
non-standard, but they're also local-dependant! So there's no decent way
we can fix the two failures you got after switching the system time zone
to Nairobi.
I'm not sure how to proceed. I'll probably end up skipping problematic
tests under Windows and maybe adding a few Windows-specific tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/17463#comment:1>
Django <https://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.
