Message337410
| Author |
steve.dower |
| 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日.17:06:23 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1551978383.93.0.210745815897.issue33944@roundup.psfhosted.org> |
| In-reply-to |
| Content |
Here's a trivial workaround for the import hook problem:
Assume we have "my_module.foo", and the import hook enables importing foo files.
Instead of just shipping "my_module.foo", you ship "my_module.py" and "_my_module.foo", where "my_module.py" looks like:
import my_import_hook
my_import_hook.install()
from _my_module import *
This really isn't hard to do. As a bonus, you don't even need a full import hook anymore - you can use any kind of loader you want. And it should be fully backwards compatible (assuming special tricks weren't part of your public API), so your users won't even notice the upgrade. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年03月07日 17:06:23 | 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, ethan smith, cheryl.sabella, Chris Billington, Peter L3 |
| 2019年03月07日 17:06:23 | steve.dower | set | messageid: <1551978383.93.0.210745815897.issue33944@roundup.psfhosted.org> |
| 2019年03月07日 17:06:23 | steve.dower | link | issue33944 messages |
| 2019年03月07日 17:06:23 | steve.dower | create |
|