[issue25500] docs claim __import__ checked for in globals, but IMPORT_NAME bytecode does not

Roundup Robot added the comment: New changeset 567baf74ebad by Brett Cannon in branch '3.5': Issue #25500: Fix the language reference to not claim that import https://hg.python.org/cpython/rev/567baf74ebad New changeset 0259c2c555fb by Brett Cannon in branch 'default': Merge for issue #25500

[issue25500] docs claim __import__ checked for in globals, but IMPORT_NAME bytecode does not

Brett Cannon added the comment: Thanks for the bug report, Sergei! I fixed the docs in the end. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue25500] docs claim __import__ checked for in globals, but IMPORT_NAME bytecode does not

Changes by Brett Cannon : -- assignee: docs@python -> brett.cannon ___ Python tracker ___

[issue25500] docs claim __import__ checked for in globals, but IMPORT_NAME bytecode does not

Brett Cannon added the comment: I think the documentation is wrong. Going all the way back to Python 2.7, you will see that importing a module emits IMPORT_NAME as the bytecode. That bytecode only looks for __import__ in the builtin namespace:

[issue25500] docs claim __import__ checked for in globals, but IMPORT_NAME bytecode does not

R. David Murray added the comment: Fix the docs. -- nosy: +r.david.murray ___ Python tracker ___ ___