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 ncoghlan
Recipients Ivan.Pozdeev, barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, mhammond, ncoghlan, pitrou, takluyver
Date 2018-06-30.06:37:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I think we also need to clearly separate two distinct aspects of .pth files:

1. "import <module>; <arbitrary code execution goes here>" lines <--- Kill it with fire
2. "<add this directory to sys.path>" lines <--- This is fine and good and perfectly sensible

It's point 2 that powers things like "pew add", and I don't see any particularly compelling reason to get rid of it.

The "arbitrary code invocation for every single Python execution using that environment" aspect, on the other hand, is mostly a PITA, and used as a workaround for other features being missing (e.g. the PYTHONRUNFIRST proposal in
Date User Action Args
2018-06-30 06:37:48ncoghlansetrecipients: + ncoghlan, mhammond, barry, brett.cannon, pitrou, eric.smith, christian.heimes, eric.snow, takluyver, Ivan.Pozdeev, ethan smith
2018-06-30 06:37:48ncoghlansetmessageid: <>
2018-06-30 06:37:48ncoghlanlinkissue33944 messages
2018-06-30 06:37:47ncoghlancreate