➜

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 Trundle, amaury.forgeotdarc, belopolsky, benjamin.peterson, brian.curtin, db3l, georg.brandl, pitrou, vstinner
Date 2011-01-03.16:39:40
SpamBayes Score 4.4538564e-09
Marked as misclassified No
Message-id <AANLkTikNLHP4_U-AsEEz=B3YSLBKh5iXNd2ZyKFJTfVb@mail.gmail.com>
In-reply-to <1294071987.12.0.843147181357.issue10814@psf.upfronthosting.co.za>
Content 
On Mon, Jan 3, 2011 at 11:26 AM, Brian Curtin <report@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.
History
Date User Action Args
2011-01-03 16:39:42belopolskysetrecipients: + belopolsky, georg.brandl, db3l, amaury.forgeotdarc, pitrou, vstinner, benjamin.peterson, Trundle, brian.curtin
2011-01-03 16:39:40belopolskylinkissue10814 messages
2011-01-03 16:39:40belopolskycreate