Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[3.11] Add re.VERBOSE flag documentation example (GH-97678)#97882

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

miss-islington
Copy link
Contributor

The current re.VERBOSE documentation example leaves space for ambiguous
interpretation. One may read that spaces within the(?: token are
spaces inside the non-capturing group (such as(?: )). This patch
removes the ambiguity by including examples after the statement.
(cherry picked from commit0ceafa7)

Co-authored-by: Athos Ribeiroathoscribeiro@gmail.com

The current re.VERBOSE documentation example leaves space for ambiguousinterpretation. One may read that spaces within the `(?:` token arespaces inside the non-capturing group (such as `(?: )`). This patchremoves the ambiguity by including examples after the statement.(cherry picked from commit0ceafa7)Co-authored-by: Athos Ribeiro <athoscribeiro@gmail.com>
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:4 of 9 required status checks are expected..

1 similar comment
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:4 of 9 required status checks are expected..

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:2 of 9 required status checks are expected..

1 similar comment
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:2 of 9 required status checks are expected..

@miss-islingtonmiss-islington merged commit0151375 intopython:3.11Oct 5, 2022
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:Pull Request is not mergeable.

3 similar comments
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:Pull Request is not mergeable.

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:Pull Request is not mergeable.

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason:Pull Request is not mergeable.

@miss-islingtonmiss-islington deleted the backport-0ceafa7-3.11 branchOctober 5, 2022 01:29
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@JelleZijlstraJelleZijlstraJelleZijlstra approved these changes

Assignees
No one assigned
Labels
docsDocumentation in the Doc dirskip issueskip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@miss-islington@JelleZijlstra@bedevere-bot@athos-ribeiro
[8]ページ先頭
©2009-2025 Movatter.jp