[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

Franklin? Lee added the comment: Petter S reported the issue to Microsoft, and got the response that it was already fixed in Insider Preview. https://github.com/microsoft/WSL/issues/3514 Should be fixed in Windows 10 version 1809, according to the tags here: https://github.com/microsoft/WSL/i

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

STINNER Victor added the comment: > 11:23:19 up -24855 days, -3:-14, 0 users, load average: 0.52, 0.58, 0.59 Impressive uptime! -- ___ Python tracker ___ __

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

Petter S added the comment: I am updating this bug since someone may find it. The problem lies with WSL. After having my computer running for many days, this is the result of the uptime command: $ uptime 11:23:19 up -24855 days, -3:-14, 0 users, load average: 0.52, 0.58, 0.59 Restarting

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

STINNER Victor added the comment: Ok, no problem, I close the issue. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

Petter S added the comment: Makes sense. I fail to reproduce it myself. :-( -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

STINNER Victor added the comment: Petter S: If you don't provide further information, I will close the issue in one week. I tried all possible ways to compile Python on Windows and I failed to reproduce the bug. I'm not saying that there is no bug, just that the bug cannot fixed it if I fai

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

Steve Dower added the comment: Also please include your sys.version. It is possible to launch Windows applications from WSL, which means we need to know if you ran the Linux version or the Windows version (though it sounds like it was a Linux version which means MS_WINDOWS is not defined).

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

STINNER Victor added the comment: Petter S: * What is your Windows version? * Which operating system are you running on WSL? Name and version? * In WSL: can you copy/paste the output of "uname -a"? What is your compiler version? Are you compiling in 32-bit or 64-bit mode? Maybe the exceptio

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

Change by STINNER Victor : -- nosy: +Petter S ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue33965] [Windows WSL] Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time, after year 2038

New submission from STINNER Victor : Petter S commented the closed bpo-25155, so I open a new issue. Copy of messages starting at https://bugs.python.org/issue25155#msg320431: msg320431 - (view) Author: Petter S (Petter S) * Date: 2018-06-25 17:52 I get this error when starting the int