Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Mon, Jan 3, 2011 at 11:26 AM, Brian Curtin <rep...@bugs.python.org> wrote:
..
>>PCbuild\amd64\python_d.exe
> Python 3.2b2+ (py3k, Jan 3 2011, 10:24:18) [MSC v.1500 64 bit (AMD64)] on
> win32
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import time
> [54931 refs]
>>>> time.asctime((12345, 1, 1, 0, 0, 0, 0, 0, 0))
> 'Mon Jan 01 00:00:00 <345'
Thanks, Brian. This is rather strange because checktm() is supposed
to convert tm_day=0 to 1:
if (buf->tm_mday == 0)
buf->tm_mday = 1;
Does time.asctime((12345, 1, 0, 0, 0, 0, 0, 0, 0)) crash on your system?
BTW, '<' in the output looks like a naive ASCII encoding for the 12-th
millennium:
12
You may need year 300,000 to observe a crash.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue10814>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
