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 p-ganssle
Recipients eamanu, eric.snow, gvanrossum, p-ganssle, vstinner, xtreak
Date 2019-02-12.16:10:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> @Guido, I recall a while back you explained the value of adding CWD to sys.path.  Would you mind providing some insight here

I think bpo-35971 or bpo-13475 are better places to discuss that, because this issue doesn't require CWD to be in the path. You can trigger this by any mechanism that would raise an exception in the Python code used to initialize the interpreter.

Even if we restrict it to the most common case - shadowing a part of the standard library - you would still be able to trigger this as long as you have *some* mechanism to manipulate the python path in the environment that allows you to put paths on there with higher precedence than the standard library.

I think the core question in this issue is whether errors in the Python code run during the interpreter initialization should crash the interpreter or exit gracefully with an error code.
Date User Action Args
2019-02-12 16:10:30p-gansslesetrecipients: + p-ganssle, gvanrossum, vstinner, eric.snow, eamanu, xtreak
2019-02-12 16:10:30p-gansslesetmessageid: <>
2019-02-12 16:10:30p-gansslelinkissue35969 messages
2019-02-12 16:10:30p-gansslecreate