[issue8013] time.asctime segfaults when given a time in the far future

[Alexander Belopolsky]

Alexander Belopolsky <alexander.belopolsky at gmail.com> added the comment:

On Sun, Jan 2, 2011 at 1:52 PM, Alexander Belopolsky
<report at 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.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8013>
_______________________________________