Message205943
| Author |
ncoghlan |
| Recipients |
Arfrever, brett.cannon, eric.snow, ncoghlan |
| Date |
2013年12月11日.23:41:59 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CADiSq7eGeEmUhgxSX6kBvivVMO60Rpv-mHAa9AHiM0=uv43oMg@mail.gmail.com> |
| In-reply-to |
<1386801725.54.0.249024980997.issue19944@psf.upfronthosting.co.za> |
| Content |
Actually, I think you make a good point. importlib.find_spec should use the
*import_module* signature (no path parameter, but with support for relative
imports). If it is exposed at all, the "one level only" single step version
should appear in importlib.machinery, not at the top level.
The current API exposes an implementation detail most users aren't going to
care about, but a "let me know if it exists but don't import it yet" API
that parallels the full dynamic import API is far more intuitive. |
|