[issue14628] Clarify import statement documentation regarding what gets bound

Changes by Brett Cannon : -- assignee: docs@python -> brett.cannon resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue14628] Clarify import statement documentation regarding what gets bound

Roundup Robot added the comment: New changeset 150bd84e737e by Brett Cannon in branch 'default': Issue #14628: Document the fact that import always returns the module http://hg.python.org/cpython/rev/150bd84e737e -- nosy: +python-dev ___ Python track

[issue14628] Clarify import statement documentation regarding what gets bound

Brett Cannon added the comment: OK, so you say "to the object found in sys.modules." -- ___ Python tracker ___ ___ Python-bugs-list m

[issue14628] Clarify import statement documentation regarding what gets bound

Eric Snow added the comment: Sounds mostly right. sys.modules[name] won't necessarily contain a module object, as Benjamin brought up in issue14609. -- ___ Python tracker ___

[issue14628] Clarify import statement documentation regarding what gets bound

Brett Cannon added the comment: So I think the sentence is saying exactly what is going on, but you want clarification that the module object is originating from sys.modules specifically. So you could change the sentence to "The first form of import statement binds the module name in the loca

[issue14628] Clarify import statement documentation regarding what gets bound

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14628] Clarify import statement documentation regarding what gets bound

New submission from Eric Snow : (see #14609 and #14582) http://docs.python.org/dev/reference/simple_stmts.html#the-import-statement The specification for the import statement says the following: "The first form of import statement binds the module name in the local namespace to the module obj