[issue37519] Three inconsistent module attributes

Eric V. Smith added the comment: While some of these might be inconsistent (I haven't really looked at it thoroughly yet), I think it might be problematic to change them at this point, since there's no doubt code out there that depends on the current behavior. -- ___

[issue37519] Three inconsistent module attributes

Change by Brett Cannon : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue37519] Three inconsistent module attributes

Change by Géry : -- nosy: +eric.snow -eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue37519] Three inconsistent module attributes

Géry added the comment: @Brett Cannon > PEPs actually become historical documents once they are implemented Actually the inconsistency of the values of the 3 module attributes (``__file__``, ``__cached__`` and ``__package__``) is with respect to the other values within the current implementa

[issue37519] Three inconsistent module attributes

Brett Cannon added the comment: PEPs actually become historical documents once they are implemented, so could you please check what the official docs say in regards to this to see if there is an inconsistency in the semantics? -- nosy: +brett.cannon _

[issue37519] Three inconsistent module attributes

New submission from Géry : Analysis In the next two sections showing the module attributes and corresponding spec attributes of imported modules and run modules, we notice the following rule (which is in accordance with this `PEP 451 section