Update import.rst #22312
Update import.rst #22312
Conversation
| to the module spec of the corresponding module or package. ``__spec__`` is | ||
| also populated when the ``__main__`` module is loaded as part of executing a | ||
| When Python is started with the :option:`-m` option, ``__main__.__spec__`` is set | ||
| to the module spec of the corresponding module or package. ``__main__.__spec__`` is |
There was a problem hiding this comment.
This change does not improve the doc. The doc explains how the __spec__ module attribute is set, the attribute in the module namespace. The name (one of the names) of the module is not relevant here.
| also populated when the ``__main__`` module is loaded as part of executing a | ||
| When Python is started with the :option:`-m` option, ``__main__.__spec__`` is set | ||
| to the module spec of the corresponding module or package. ``__main__.__spec__`` is | ||
| also populated when the :mod:`__main__` module is loaded as part of executing a |
There was a problem hiding this comment.
Code markup is used on purpose to avoid creating 50 links when a module or function is named 50 times in a paragraph, that’s why there is :mod:__main__ on line 982 but just __main__ here.
There was a problem hiding this comment.
@merwok Instead of manual markup, can pydoc be taught to create a link for the first occurence in a paragraph only? It will allow to not bother about visual pleasure and focus on semantics (an abstract examplelish notion vs a concrete field).
This minor PR adds missing prefixes
__main__.and formatting tags:mod:in the section 5.8. Special considerations for __main__ of the import system documentation.