[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Srinivas Reddy Thatiparthy(శ్రీనివాస్ రెడ్డి తాటిపర్తి) added the comment: Yikes, Sorry for the spam. I should have double checked. -- ___ Python tracker ___

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

STINNER Victor added the comment: Hi, """ This bug is happening for 3.6 too. Please see below, (...) File "/home/dtdev/virtual/upwork/lib/python3.6/site-packages/pip/_vendor/requests/packages/urllib3/util/connection.py", line 85, in create_connection sock.settimeout(timeout)

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Srinivas Reddy Thatiparthy(శ్రీనివాస్ రెడ్డి తాటిపర్తి) added the comment: This bug is happening for 3.6 too. Please see below, 18:14 $ python --version Python 3.6.3 (upwork) ✔ ~/workspace/personal/assignment [master|✔] 18:16 $ pip install --upgrade pip Exception: Traceback (most recent

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

STINNER Victor added the comment: I created bpo-33965: [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038. -- ___ Python tracker

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Petter S added the comment: I also compiled Python myself on WSL. The bug seemed to appear after computer had been running for a while. Before that, the interpreters were working normally. And after rebooting the problem disappeared. -- ___

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

STINNER Victor added the comment: 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,

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

STINNER Victor added the comment: > I get this error when starting the interpreter in Windows subsystem for Linux > (WSL). This bug is currently closed, please open a new bug. About your issue. I'm not sure if Windows subsystem for Linux is officially supported. How did you install Python

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Petter S added the comment: I get this error when starting the interpreter in Windows subsystem for Linux (WSL). I am using Python 2.7.15rc1 $ python --version Python 2.7.15rc1 $ python Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Petter S added the comment: For Python 3: $ python3 --version Python 3.7.0b3 $ python3 Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time OverflowError: timestamp too large to convert to C _PyTime_t Current thread 0x7f0232c21080 (most recent call first): Aborted

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Changes by STINNER Victor : -- keywords: +3.5regression ___ Python tracker ___ ___

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Changes by STINNER Victor : -- title: datetime.datetime.now() raises -> Windows: datetime.datetime.now() raises an OverflowError for date after year 2038 ___ Python tracker

[issue25155] Windows: datetime.datetime.now() raises an OverflowError for date after year 2038

Roundup Robot added the comment: New changeset f1cc1f379b00 by Victor Stinner in branch '3.5': Issue #25155: Fix _PyTime_Divide() rounding https://hg.python.org/cpython/rev/f1cc1f379b00 -- ___ Python tracker