Clarify the meaning of "name".

This commit is contained in:
Eric Snow 2013-10-07 11:01:48 -06:00
parent d52a386e82
commit d96d7091d6
1 changed files with 11 additions and 4 deletions

View File

@ -37,6 +37,13 @@ is a brief summary of all three groups of terms and concepts. A more
detailed explanation of the import system is found at
[import_system_docs]_.
name
----
In this proposal, a module's "name" refers to its fully-qualified name,
meaning the fully-qualified name of the module's parent (if any) joined
to the simple name of the module by a period.
finder
------
@ -240,7 +247,7 @@ A specification for a module's import-system-related state. See the
Attributes:
* name - a string for the name of the module.
* name - a string for the fully-qualified name of the module.
* loader - the loader to use for loading.
* origin - the name of the place from which the module is loaded,
e.g. "builtin" for built-in modules and the filename for modules
@ -251,8 +258,8 @@ Attributes:
during loading.
* cached (property) - a string for where the compiled module should be
stored.
* parent (RO-property) - the name of the package to which the module
belongs as a submodule (or None).
* parent (RO-property) - the fully-qualified name of the package to
which the module belongs as a submodule (or None).
* has_location (RO-property) - a flag indicating whether or not the
module's "origin" attribute refers to a location.
@ -547,7 +554,7 @@ a list (even an empty one). Otherwise it is None.
The name of the corresponding module attribute, ``__path__``, is
relatively ambiguous. Instead of mirroring it, we use a more explicit
name that makes the purpose clear.
attribute name that makes the purpose clear.
**loader_state**