➜

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 tim.golden
Recipients Ramchandra Apte, belopolsky, flox, patrick.vrijlandt, tim.golden, vstinner
Date 2011-12-30.10:24:59
SpamBayes Score 0.00041348304
Marked as misclassified No
Message-id <4EFD9177.6000101@timgolden.me.uk>
In-reply-to <1325198306.53.0.729167535996.issue13674@psf.upfronthosting.co.za>
Content 
Well, the code in 2.x is quite different from that in 3.x.
Specifically, the 2.x code assumes that, for Windows, no
year before 1900 is valid for any of the formats. So a
simple check throws a ValueError for tm_year < 0. For 3.x
the assumption was that Windows can handle any year as far
back as 0; in fact that's not true for the %y format.

I'll propose a patch to timemodule.c but I'll have to take
it to python-dev as I'm not 100% sure of the best place for
it.
History
Date User Action Args
2011-12-30 10:25:00tim.goldensetrecipients: + tim.golden, belopolsky, vstinner, flox, patrick.vrijlandt, Ramchandra Apte
2011-12-30 10:24:59tim.goldenlinkissue13674 messages
2011-12-30 10:24:59tim.goldencreate