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 SilentGhost, Trundle, belopolsky, georg.brandl, l0nwlf, ned.deily, sandro.tosi, vstinner, wsanchez
Date 2011-01-03.00:02:12
SpamBayes Score 5.1843676e-07
Marked as misclassified No
Message-id <1294012947.93.0.785881229399.issue8013@psf.upfronthosting.co.za>
In-reply-to
Content
Backported in r87664 (2.6), r87663 (2.7) and r87662 (3.1).

Reopening to implement bounds checking for 3.2.  Note that for time.asctime, checking the year range is trivial, but for time.ctime it is not because year is not computed in python code.  One solution may be to check bounds of the time_t timestamp, but those depend on the timezone.  Maybe it is easiest to simply call mktime(), check year and call asctime() bypassing OS ctime completely.
History
Date User Action Args
2011-01-03 00:02:28belopolskysetrecipients: + belopolsky, georg.brandl, wsanchez, vstinner, ned.deily, Trundle, SilentGhost, sandro.tosi, l0nwlf
2011-01-03 00:02:27belopolskysetmessageid: <1294012947.93.0.785881229399.issue8013@psf.upfronthosting.co.za>
2011-01-03 00:02:12belopolskylinkissue8013 messages
2011-01-03 00:02:12belopolskycreate