Antoine Pitrou added the comment: Ah, ok. So it's a controlled crash: Python fails initializing the standard streams and so it decides to bail out (by using Py_FatalError, since Py_Initialize doesn't return an error code).
What we could do is call initsigs() after initstdio() (but still before initsite(), since initsite() can call arbitrary Python code). I'm a bit surprised that you manage to press Ctrl-C so fast that it occurs right during initialization of standard streams, by the way :-) ---------- nosy: +haypo, pitrou title: Ctrl-C causes startup crashes on Windows -> Ctrl-C at startup can end in a Py_FatalError call versions: -Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19983> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
