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 eric.smith
Recipients Anthony Sottile, Chris Billington, Ivan.Pozdeev, Peter L3, SilentGhost, __Vano, barry, brett.cannon, cheryl.sabella, christian.heimes, eric.smith, eric.snow, ethan smith, ionelmc, jaraco, mhammond, ncoghlan, pitrou, steve.dower, takluyver, terry.reedy, veky
Date 2019-03-07.20:46:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1551991565.92.0.403387122952.issue33944@roundup.psfhosted.org>
In-reply-to
Content
>> I should have to start that package somehow.
>
> `pip install` is a pretty good opt-in already imo

I think that’s where we disagree. Like others, I don’t want this to affect every python script in a given installation. 

>> Instead of just shipping "my_module.foo", you ship "my_module.py" and "_my_module.foo", where "my_module.py" looks like:
>
> but that's exactly my point, now you have to ship extra junk python files when it's a way better experience to have the hooks _just work_


You mean extra junk like .pth files? I don’t see the difference between a .py file and a .pth file, except I can’t opt out of .pth files. 

We’re just looking for some way to control the behavior, without giving the .pth file unlimited capabilities before the user script starts. If it’s “just” some extra .py files, then maybe that’s great. If we need some other new mechanism, then I’d be okay with that, too.
History
Date User Action Args
2019-03-07 20:46:05eric.smithsetrecipients: + eric.smith, mhammond, barry, brett.cannon, terry.reedy, jaraco, ncoghlan, pitrou, christian.heimes, ionelmc, SilentGhost, __Vano, eric.snow, takluyver, steve.dower, veky, Ivan.Pozdeev, Anthony Sottile, ethan smith, cheryl.sabella, Chris Billington, Peter L3
2019-03-07 20:46:05eric.smithsetmessageid: <1551991565.92.0.403387122952.issue33944@roundup.psfhosted.org>
2019-03-07 20:46:05eric.smithlinkissue33944 messages
2019-03-07 20:46:05eric.smithcreate