PEP 661: Amend to allow two customizations

[JelleZijlstra]

These are changes I'd like to make during the beta phase (I'll post asking for SC approval).

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #32627747 | 📁 Comparing 7dd698f against latest (0cde95d)

  🔍 Preview build  

699 files changed · ± 699 modified

± Modified

• pep-0001/index.html
• pep-0002/index.html
• pep-0003/index.html
• pep-0004/index.html
• pep-0005/index.html
• pep-0006/index.html
• pep-0007/index.html
• pep-0008/index.html
• pep-0009/index.html
• pep-0010/index.html
• and 689 more...

[taleinat]

Both of these, customizable repr and setting __module__, were in earlier versions of the PEP and make sense.

Regarding making repr customizable by passing in an argument, LGTM.

Regarding making __module__ writeable, I find that a bit surprising. Have you considered adding another argument to sentinel()? That would be more in line with namedtuple and Enum which do this for similar reasons, and be more in line with sentinels being immutable. (I see Kyle made a similar comment in the PEP discussion.)