| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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 commit 0ceafa7) Co-authored-by: Athos Ribeiro <athoscribeiro@gmail.com>
|
Sorry, I can't merge this PR. Reason: 4 of 9 required status checks are expected.. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: 4 of 9 required status checks are expected.. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: 2 of 9 required status checks are expected.. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: 2 of 9 required status checks are expected.. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: Pull Request is not mergeable. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: Pull Request is not mergeable. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: Pull Request is not mergeable. |
Sorry, something went wrong.
|
Sorry, I can't merge this PR. Reason: Pull Request is not mergeable. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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 commit 0ceafa7)
Co-authored-by: Athos Ribeiro athoscribeiro@gmail.com