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 eamanu, eric.snow, p-ganssle, vstinner, xtreak
Date 2020-05-15.01:01:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I agree with @p-ganssle, If exist some problem on initialize Python interpreter it would be great if it return a non-zero status and avoid an abort()

Since Python 3.8 (PEP 587), Python no longer call abort() on initialization error.

$ echo bug >

$ PYTHONPATH=$PWD python3.8 -c pass
Fatal Python error: init_sys_streams: can't initialize sys standard streams
Python runtime state: core initialized
Traceback (most recent call last):
  File "/usr/lib64/python3.8/", line 52, in <module>
  File "/home/vstinner/", line 1, in <module>
NameError: name 'bug' is not defined

I don't think that it's worth it to change Python 3.7.

The initial issue was that abort() was called in this case. It's no longer the case, so I close the issue.

If someone cares abou the more general issue with the current directory being added to sys.path, please open a separated issue (or look for existing issues).
Date User Action Args
2020-05-15 01:01:35vstinnersetrecipients: + vstinner, eric.snow, p-ganssle, eamanu, xtreak
2020-05-15 01:01:35vstinnersetmessageid: <>
2020-05-15 01:01:35vstinnerlinkissue35969 messages
2020-05-15 01:01:34vstinnercreate