Nick Coghlan <ncogh...@gmail.com> added the comment:
dw: we routinely impose new requirements on folks modifying runtime internals in new feature releases, so the only aspect we missed for this changing is to explicitly call it out in the Porting section of the Python 3.6 What's New document as a potential forward compatibility risk for import system replacement authors that don't update their plugins accordingly. For folks implementing PEP 302 finders and loaders, no change is required, as they indicate failure to find a module by returning None, not by raising ImportError. It's only folks emulating the full import system by replacing `__import__` that should need to worry about this. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35486> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
