-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 675: Clarify wording in various sections #2279
Conversation
There was already a Backwards Compatibility heading for Type Inference. So, I just inlined the second one into the Runtime Behavior section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent job on the writing, @pradeep90 . I just had a few rst/PEP syntax and formatting comments.
We had two "sections" - one for the type inference and one for the runtime behavior. Move them both into one top-level section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @pradeep90 ! I'll let @JelleZijlstra review and merge, being the PEP sponsor.
Mostly just nits.
Remaining: Add an exhaustive list of
str
methods that we will modify. I'm making that a separate PR for ease of review.cc @gbleaney