Message336709
| Author | steve.dower |
|---|---|
| Recipients | Anthony Sottile, Chris Billington, Ivan.Pozdeev, SilentGhost, __Vano, barry, brett.cannon, cheryl.sabella, christian.heimes, emma_smith, eric.smith, eric.snow, ionelmc, jaraco, mhammond, ncoghlan, pitrou, steve.dower, takluyver, terry.reedy, veky |
| Date | 2019-02-26.20:32:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1551213144.95.0.64457862021.issue33944@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Extending sys.path is a useful use case, but doing so in pth files is problematic. There are 100 other ways to end up in this situation though. Why is *this* one so much worse? Can you offer an issue you hit that was caused by a .pth file that *wasn't* debuggable by listing sys.path? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-02-26 20:32:24 | steve.dower | set | recipients: + steve.dower, mhammond, barry, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, eric.smith, christian.heimes, ionelmc, SilentGhost, __Vano, eric.snow, takluyver, veky, Ivan.Pozdeev, Anthony Sottile, emma_smith, cheryl.sabella, Chris Billington |
| 2019-02-26 20:32:24 | steve.dower | set | messageid: <1551213144.95.0.64457862021.issue33944@roundup.psfhosted.org> |
| 2019-02-26 20:32:24 | steve.dower | link | issue33944 messages |
| 2019-02-26 20:32:24 | steve.dower | create | |