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 SilentGhost, Trundle, belopolsky, georg.brandl, ned.deily, sandro.tosi, vstinner, wsanchez
Date 2011-01-03.12:27:06
SpamBayes Score 0.009244364
Marked as misclassified No
Message-id <1294057631.91.0.0155272491228.issue8013@psf.upfronthosting.co.za>
In-reply-to
Content
> http://docs.python.org/library/time.html#time-y2kissues
> "Values 100–1899 are always illegal."

Why are these values illegal? The GNU libc accepts year in [1900-2^31; 2^31-1] (tm_year in [-2147483648; 2147481747]). If time.accept2dyear=False, we should at least accept years in [1; 9999]. The system libc would raise an error (return NULL) if it doesn't know how to format years older than 1900.
History
Date User Action Args
2011-01-03 12:27:11vstinnersetrecipients: + vstinner, georg.brandl, belopolsky, wsanchez, ned.deily, Trundle, SilentGhost, sandro.tosi
2011-01-03 12:27:11vstinnersetmessageid: <1294057631.91.0.0155272491228.issue8013@psf.upfronthosting.co.za>
2011-01-03 12:27:06vstinnerlinkissue8013 messages
2011-01-03 12:27:06vstinnercreate