homepage

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 lemburg
Recipients Eli Collins, belopolsky, lemburg
Date 2017年01月22日.18:52:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485111162.46.0.402379452127.issue29346@psf.upfronthosting.co.za>
In-reply-to
Content
According to the datetime.h file, the valid range for year is 1-9999, so it's a bit surprising that Python 3.6 allows dates outside this range.
Internally, the year is represented using 2 bytes, so you could represent years outside the range and up to 65535 as well.
Here's what mxDateTime outputs for the given timestamps:
 >>> from mx.DateTime import *
 >>> DateTimeFromTicks(1<<40)
<mx.DateTime.DateTime object for '36812-02-20 01:36:16.00' at 7f17a38a2390>
 >>> DateTimeFromTicks(1<<41)
<mx.DateTime.DateTime object for '71654-04-10 03:12:32.00' at 7f17a1bdf858>
History
Date User Action Args
2017年01月22日 18:52:42lemburgsetrecipients: + lemburg, belopolsky, Eli Collins
2017年01月22日 18:52:42lemburgsetmessageid: <1485111162.46.0.402379452127.issue29346@psf.upfronthosting.co.za>
2017年01月22日 18:52:42lemburglinkissue29346 messages
2017年01月22日 18:52:42lemburgcreate

AltStyle によって変換されたページ (->オリジナル) /