➜

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 vstinner
Recipients Petter S, belopolsky, josh.r, paul.moore, python-dev, steve.dower, tim.golden, vmurashev, vstinner, zach.ware
Date 2018-06-25.22:05:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529964337.23.0.56676864532.issue25155@psf.upfronthosting.co.za>
In-reply-to
Content 
I tried 64-bit builds of Python 2.7 and 3.7rc1 (binaries from python.org) on Windows 10 on year 2045: start with no error, time.time() and datetime.datetime.now() don't fail.

I tried Python 2.7.12 and 3.5.2 on Ubuntu 16.04 in WSL on my Windows 10: same, start with no error, time.time() and datetime.datetime.now() don't fail. It's 64-bit Ubuntu with 64-bit binaries for Python 2 and Python 3 (check sys.maxsize).

I even compiled Python 2.7.15 and 3.7rc1 on Ubuntu 16.04 in WSL on my Windows 10: same again, start with no error, time.time() and datetime.datetime.now() don't fail. Python 2 and 3 have been compiled in 64-bit mode, since it's a 64-bit Ubuntu.

Everything is fine. I failed to reproduce your bug.
History
Date User Action Args
2018-06-25 22:05:37vstinnersetrecipients: + vstinner, paul.moore, belopolsky, tim.golden, python-dev, zach.ware, steve.dower, vmurashev, josh.r, Petter S
2018-06-25 22:05:37vstinnersetmessageid: <1529964337.23.0.56676864532.issue25155@psf.upfronthosting.co.za>
2018-06-25 22:05:37vstinnerlinkissue25155 messages
2018-06-25 22:05:37vstinnercreate