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 vstinner
Recipients belopolsky, musically_ut, ned.deily, serhiy.storchaka, vstinner
Date 2017-07-10.08:39:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I reverted the commit which fixes test_datetime to also test Lib/, to repair buildbots. But since I reverted the change, nothing was done so is still not tested :-(

> The tests enabled by "-utzdata" check UTC to local and back conversions at several points around *every* time transition in *every* timezone. On systems with a complete installation of IANA tzdata, this is a lot of test points.
> These tests were supposed to be exhaustive and I did not expect them to be run by default.  that's why I introduced the -utzdata flag in the first place.

Alexander: yeah, having an opt-in option to test all timezones makes sense. It's likely to trigger bugs in some corner cases. But the question is really having our CI.

Alexander, Serhiy: would you be ok to disable tzdata resource on all our CI (Travis CI, AppVeyor, all buildbots)?

*Maybe* we might enable tzdata on selected (fast) buildbots where test_datetime takes less than 20 minutes. But I would prefer to keep the option as an *opt-in*, rather than always running all tests on all CI.
Date User Action Args
2017-07-10 08:39:31vstinnersetrecipients: + vstinner, belopolsky, ned.deily, serhiy.storchaka, musically_ut
2017-07-10 08:39:31vstinnersetmessageid: <>
2017-07-10 08:39:31vstinnerlinkissue30822 messages
2017-07-10 08:39:30vstinnercreate