PEP 842: New revision based on discussion feedback

[ZeroIntensity]

• 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)

---

@hugovk -- Not too sure who to ping, but I added a Sphinx extension to highlight custom keywords. Is that okay? It's not too complex, and I think it makes the proposed syntax look really nice.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33949241 | 📁 Comparing 4a25b2e against latest (0475dc3)

  🔍 Preview build  

9 files changed · ± 9 modified

± Modified

• index.html
• numerical/index.html
• pep-0000/index.html
• pep-0719/index.html
• pep-0745/index.html
• pep-0764/index.html
• pep-0833/index.html
• pep-0842/index.html
• topic/packaging/index.html

[ZeroIntensity]

Echoing what I said on DPO: If nobody has any complaints about the Sphinx plugin here, I'll merge this today or tomorrow (partially depending on when Barry posts PEP 844).

[hugovk]

Can you split out the extension to another PR? Then we don't need to delay the PEP update.

[ZeroIntensity]

I can, but I'm hesitant to do so, since it makes the proposed solution look pretty bad :(

The highlighting makes it feel way more natural.

[ZeroIntensity]

I'm going to try out GitHub's fancy new PR stacking thing for the Sphinx extension.

[ZeroIntensity]

After careful analysis, it seems that it did not work at all. I'm going to merge this and put up the highlighting in a new PR.