➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients ajaksu2, akuchling, barry, belopolsky, doerwalter, eric.araujo, python-dev, r.david.murray, tim.peters
Date 2012-08-22.02:38:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345603111.43.0.633030139523.issue665194@psf.upfronthosting.co.za>
In-reply-to
Content 
> So since the other tests were passing before, presumably there
> is some test that could be added to exercise the bug you were
> fixing.  Do you remember what that was?

Yes, the issue was the one that was mentioned in an XXX comment: in many places UTC offset was different at different historical times but standard C library and Python's time module provides a single constant for it.  There are plenty of examples that can be found in Olson's database (Europe/Kiev comes to mind), but it is not easy to devise a test that will work cross-platform.  Maybe we should just restrict the test to Linux/BSD family of OSes?
History
Date User Action Args
2012-08-22 02:38:31belopolskysetrecipients: + belopolsky, tim.peters, barry, akuchling, doerwalter, ajaksu2, eric.araujo, r.david.murray, python-dev
2012-08-22 02:38:31belopolskysetmessageid: <1345603111.43.0.633030139523.issue665194@psf.upfronthosting.co.za>
2012-08-22 02:38:30belopolskylinkissue665194 messages
2012-08-22 02:38:30belopolskycreate