Message337408
| Author | steve.dower |
|---|---|
| Recipients | Anthony Sottile, Chris Billington, Ivan.Pozdeev, Peter L3, 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-03-07.16:59:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1551977993.93.0.074502868415.issue33944@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Elaborate please, as it sounds like you're simply dismissing my usecase. I'm suggesting that to enable this functionality at startup, the user/application should have to do something like executing code or setting PYTHONSTARTUP. What I'm dismissing is that "pip install some-package" can define a global startup task for your interpreter. I shouldn't get debugging or code coverage enabled every time I run "python" just because I installed some package - I should have to start that package somehow. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-07 16:59:53 | 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, Peter L3 |
| 2019-03-07 16:59:53 | steve.dower | set | messageid: <1551977993.93.0.074502868415.issue33944@roundup.psfhosted.org> |
| 2019-03-07 16:59:53 | steve.dower | link | issue33944 messages |
| 2019-03-07 16:59:53 | steve.dower | create | |