Message320754
| Author | ncoghlan |
|---|---|
| Recipients | Ivan.Pozdeev, barry, brett.cannon, christian.heimes, emma_smith, eric.smith, eric.snow, mhammond, ncoghlan, pitrou, takluyver |
| Date | 2018-06-30.06:37:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1530340668.37.0.56676864532.issue33944@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 https://bugs.python.org/issue14803). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-06-30 06:37:48 | ncoghlan | set | recipients: + ncoghlan, mhammond, barry, brett.cannon, pitrou, eric.smith, christian.heimes, eric.snow, takluyver, Ivan.Pozdeev, emma_smith |
| 2018-06-30 06:37:48 | ncoghlan | set | messageid: <1530340668.37.0.56676864532.issue33944@psf.upfronthosting.co.za> |
| 2018-06-30 06:37:48 | ncoghlan | link | issue33944 messages |
| 2018-06-30 06:37:47 | ncoghlan | create | |