➜

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:52:34
SpamBayes Score 4.8715143e-11
Marked as misclassified No
Message-id <AANLkTi=Wdih8TkdP6AyO-j-gJNYv+V7ZHJo5x2ANB9Ji@mail.gmail.com>
In-reply-to <1293983579.55.0.974869919023.issue8013@psf.upfronthosting.co.za>
Content 
On Sun, Jan 2, 2011 at 10:52 AM, Georg Brandl <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.

> On the other hand, it seems that implementations either return a correct string or NULL,
> so just erroring out in case of NULL would be fine as well.

This is true on the platforms that I have access to: OSX, Linux, and
Solaris.  I think asctime_r is available and behaves this way on
Python supported platforms.  I'll check this in and watch the bots.
History
Date User Action Args
2011-01-02 18:52:36Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, georg.brandl, belopolsky, wsanchez, ned.deily, Trundle, sandro.tosi, l0nwlf
2011-01-02 18:52:34Alexander.Belopolskylinkissue8013 messages
2011-01-02 18:52:34Alexander.Belopolskycreate