Message333638
| Author |
barry |
| Recipients |
Anthony Sottile, Chris Billington, Ivan.Pozdeev, SilentGhost, __Vano, barry, brett.cannon, christian.heimes, eric.smith, eric.snow, ethan smith, jaraco, mhammond, ncoghlan, pitrou, takluyver, terry.reedy, vstinner |
| Date |
2019年01月14日.19:55:22 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<2C557906-6A18-4A90-8439-A7F328D97F4D@python.org> |
| In-reply-to |
<1547456518.6.0.169335368433.issue33944@roundup.psfhosted.org> |
| Content |
On Jan 14, 2019, at 04:02, STINNER Victor <report@bugs.python.org> wrote:
>
> I really hate .pth files because the slow down Python startup time for *all* applications whereas .pth files are usually specific to a very few applications using one or two specific modules.
>
> They can also modify the behavior of Python for all applications, with no way to opt-out.
>
> I would prefer to have an opt-in option, disabled by default.
I completely agree. The other problem is that .pth-caused problems are very difficult to diagnose and debug. Essentially you have to hack site.py to break into the loading machinery. I have to believe that we can come up with a better mechanism that doesn’t suffer from these problems.
Do we have a single place to capture a list of .pth use cases? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年01月14日 19:55:23 | barry | set | recipients:
+ barry, mhammond, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, vstinner, eric.smith, christian.heimes, SilentGhost, __Vano, eric.snow, takluyver, Ivan.Pozdeev, Anthony Sottile, ethan smith, Chris Billington |
| 2019年01月14日 19:55:22 | barry | link | issue33944 messages |
| 2019年01月14日 19:55:22 | barry | create |
|