[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

STINNER Victor added the comment: > Hmm, I've managed to produce the error with 3.1: Oh oh, I thought that importlib changed the behaviour, but I'm wrong. importlib doesn't change anything so I'm closing the issue as invalid. -- resolution: -> invalid status: open -> closed

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Terry J. Reedy added the comment: In a running interpreter and Idle, ^C results in KeyboardInterrupt >>> and nothing else. >From a command line, I think KeyboardInterrupt: Python startup stopped" would be ideal. On Windows, I do not know if a program started from an icon, shortcut, or explo

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Stefan Krah added the comment: The funny thing is, in 3.3 I can't reproduce it (i.e. I only get the KeyboardInterrupt). So I'm not sure if this happens more often now. ^CTraceback (most recent call last): File "", line 989, in _find_and_load File "", line 571, in load_module File "", lin

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Brett Cannon added the comment: So importlib just increased the window of vulnerability for this kind of thing. -- ___ Python tracker ___ ___

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Stefan Krah added the comment: Hmm, I've managed to produce the error with 3.1: $ python3.1 Fatal Python error: Py_Initialize: can't initialize sys standard streams Traceback (most recent call last): File "/usr/lib/python3.1/io.py", line 60, in import _io File "/usr/lib/python3.1/os.py

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Brett Cannon added the comment: Welcome to Python code running during startup. =) As I said, the only thing I can think of is raising the exception instead of catching it and immediately triggering the fatal exception, but that specific fatal error was not introduced by me so this is just a s

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

STINNER Victor added the comment: > OK, so what's your point? =) In Python < 3.3, CTRL+c at startup fails with "Traceback: ...", not with a fatal error. A fatal error may dump a core dump and open a popup on Windows. -- ___ Python tracker

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

R. David Murray added the comment: I think Victor's point was that you get the "can't initialize standard streams" in addition to the KeyboardInterrupt (but I'm just guessing). (See issue 14228 for examples of what normally happens on a startup KeyboardInterrupt.) -- nosy: +r.david.m

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Brett Cannon added the comment: OK, so what's your point? =) I mean you stopped the interpreter while in the middle of starting up. Do you want to trigger a fatal error if the exception raised was KeyboardInterrupt? -- ___ Python tracker

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14627] Fatal Python Error when Python startup is interrupted by CTRL+c

New submission from STINNER Victor : If you press CTRL+c while Python is starting, you may get such error: ^CFatal Python error: Py_Initialize: can't initialize sys standard streams Traceback (most recent call last): File "", line 990, in _find_and_load File "", line 571, in load_module Fi