fix: use unambiguous punction in 'invalid escape sequence' message #26582
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pablogsal
approved these changes
Jun 8, 2021
|
Thanks @nedbat for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Jun 8, 2021
…ythonGH-26582) (cherry picked from commit ffd87b7) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
GH-26590 is a backport of this pull request to the 3.10 branch. |
|
Thanks @nedbat for the catch and the PR! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds quotes around the syntax error for invalid escape sequences. This matches the messages in bytesobject.c and unicodeobject.c. My invalid escape sequence was backslash-space. This change made it easier to understand what I was being told.