PEP 802: Amend wording of single-token rejected alternative by jb2170 · Pull Request #4938 · python/peps
- 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)
Summary
I love that my discussion post made it into the PEP, but a slight change of characterisation is needed:
I discussed whether {/} should be added as a single token or three separate ones. I didn't propose it. I'm in favour of allowing spaces. 😅
I love this PEP btw.
Commits
- 74d11ba: Typos
- 35163be: Change 'bracket' to 'brace' for
{and}. Do cherry pick this out it it's insulting pedantry - 4788b16: Main commit amending the wording referring to my post
Thanks!
📚 Documentation preview 📚: https://pep-previews--4938.org.readthedocs.build/