[issue15292] import hook behavior documentation improvement

Brett Cannon added the comment: Closing as "works for me" due to lack of reply from OP. -- resolution: -> works for me status: pending -> closed ___ Python tracker ___ _

[issue15292] import hook behavior documentation improvement

Brett Cannon added the comment: So I can't reproduce the problem under Python 2.7.3, Python 3.2.3, or a fresh checkout of Python 3.3. This is with both your script, Anders, and writing my own class that defined find_module() to just raise ImportError that I set in either sys.meta_path or in s

[issue15292] import hook behavior documentation improvement

Nick Coghlan added the comment: Perhaps the porting section in the 3.3 What's New? -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue15292] import hook behavior documentation improvement

Brett Cannon added the comment: Everything Nick said is right: PyPy did it properly according to the spec and CPython 2.7 got it wrong. Unfortunately fixing this now would break code and so it will simply have to stay a Python 2.7 quirk with Python 3.3 and later doing it correctly. So docume

[issue15292] import hook behavior documentation improvement

Nick Coghlan added the comment: The PyPy and 3.3 behaviour are actually correct according to the spec, but it's *really* unclear in PEP 302. sys.meta_path accepts finder objects. These are explicitly documented as returning "None" from find_module() to indicate "try the next one" and raising

[issue15292] import hook behavior documentation improvement

Changes by Antoine Pitrou : -- nosy: +brett.cannon, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue15292] import hook behavior documentation improvement

New submission from Anders Hammarquist : When testing Eutaxia on PyPy (1.9) I discovered a discrepancy in the path_hooks import hook implementation. In CPython (2.7), if the find_module() method raises ImportError (as imp.find_module() does when it does not find a module in the given path), wi