Skip to content

PEP 802: Amend wording of single-token rejected alternative#4938

Open
jb2170 wants to merge 3 commits intopython:mainfrom
jb2170:pep-802-single-token
Open

PEP 802: Amend wording of single-token rejected alternative#4938
jb2170 wants to merge 3 commits intopython:mainfrom
jb2170:pep-802-single-token

Conversation

@jb2170
Copy link
Copy Markdown
Contributor

@jb2170 jb2170 commented Apr 26, 2026

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

jb2170 added 3 commits April 26, 2026 01:21
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.
@jb2170 jb2170 requested a review from AA-Turner as a code owner April 26, 2026 00:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants