Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 696: some suggestions to make the text clearer #3641

Merged
merged 8 commits into from
Feb 8, 2024

Conversation

rchen152
Copy link
Contributor

@rchen152 rchen152 commented Feb 6, 2024

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

I've made some suggested edits to the text for readability and fixed what I think is a typo in a code example. Feel free to reject any edits that don't make sense.

cc @Gobot1234


📚 Documentation preview 📚: https://pep-previews--3641.org.readthedocs.build/

* Moves TypeVarTuple discussion so the text flows better. Otherwise, it
  feels to me like an awkward interlude between the paragraph
  introducing rules and the actual rules.
* Does some light grammar massaging of said introductory paragraph.
In sections where the text uses `T1` and `T2` as TypeVar names, changes
the examples to use the same names.
I'm pretty sure this is backwards, as it's the opposite of what
"Constraint Rules" says, and the latter makes more sense to me.
Spells out subclassing rules in the text, rather than leaning so much on
the example.
@rchen152 rchen152 requested a review from Gobot1234 February 7, 2024 23:43
@JelleZijlstra JelleZijlstra merged commit 2b91368 into python:main Feb 8, 2024
6 checks passed
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.

3 participants