➜

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 Alexander.Belopolsky
Recipients Alexander.Belopolsky, Trundle, belopolsky, georg.brandl, l0nwlf, ned.deily, sandro.tosi, wsanchez
Date 2011-01-02.18:59:09
SpamBayes Score 6.625096e-07
Marked as misclassified No
Message-id <AANLkTin3eyiDOoO+LNdzONrdj_m3TRzYV1DJemVo4K=O@mail.gmail.com>
In-reply-to <AANLkTi=Wdih8TkdP6AyO-j-gJNYv+V7ZHJo5x2ANB9Ji@mail.gmail.com>
Content 
On Sun, Jan 2, 2011 at 1:52 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
..
>> Well, then I would have no problem with checking for that condition beforehand and raising
>> ValueError.
>>
>
> IIRC, there was a similar bug report about ctime where pre-condition
> checking was required because platform ctime would crash for huge
> values of time.  I'll try to find the ticket.

Hmm. My search brought up issue 10563, but the last message on that
issue says that "a change has been recently made to time.asctime() to
reject year > 9999.  See r85137 and issue6608."  I wonder if that
change made this issue moot.
History
Date User Action Args
2011-01-02 18:59:13Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, georg.brandl, belopolsky, wsanchez, ned.deily, Trundle, sandro.tosi, l0nwlf
2011-01-02 18:59:09Alexander.Belopolskylinkissue8013 messages
2011-01-02 18:59:09Alexander.Belopolskycreate