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 675: Clarify wording in various sections #2279

Merged
merged 8 commits into from
Jan 27, 2022

Conversation

pradeep90
Copy link
Contributor

@pradeep90 pradeep90 commented Jan 26, 2022

Mostly just nits.

  • Ease into the Motivation section for people who are unfamiliar with security stuff.
  • Forward-reference the Other Uses section at the end of Motivation

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

Copy link
Member

@CAM-Gerlach CAM-Gerlach left a 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.

pep-0675.rst Outdated Show resolved Hide resolved
pep-0675.rst Outdated Show resolved Hide resolved
We had two "sections" - one for the type inference and one for the
runtime behavior. Move them both into one top-level section.
@pradeep90 pradeep90 requested a review from CAM-Gerlach January 26, 2022 22:50
Copy link
Member

@CAM-Gerlach CAM-Gerlach left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants