This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients FFY00, barry, brett.cannon, eric.snow, iritkatriel, ncoghlan, pitrou, pmpp, rhettinger
Date 2021-10-21.00:20:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
On Oct 20, 2021, at 08:18, Eric Snow <> wrote:

> The spec identifies how a module should be loaded (or how it was loaded and should be reloaded).  We should be careful to preserve that identify and not invite uses to modify the spec after (or while) the module is loaded.  PEP 451 talks about the difference a little, but I'm pretty sure it came up in more detail in discussions about the PEP at that time.

It’s frankly not good enough to capture the *intent* of these attributes in a PEP.  We need to be clear in the documentation about their purpose and we need to be clear about when to use or set either the module attribute or the spec attribute.  The current situation is ambiguous and possibly misleading.  But maybe it’s “just” a documentation issue?
Date User Action Args
2021-10-21 00:20:43barrysetrecipients: + barry, brett.cannon, rhettinger, ncoghlan, pitrou, pmpp, eric.snow, FFY00, iritkatriel
2021-10-21 00:20:43barrylinkissue33277 messages
2021-10-21 00:20:43barrycreate