Fix deprecated Python string literal escape sequence #296
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
|
Hi all! Is it possible to merge this PR? As is, we're having trouble using this library |
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.
These regular expressions are intending to "escape" the
-so that it's not treated as a range inside of the[ ... ]regex character class-- but Python sees this as a string literal containing the escape sequence\-.Starting in Python 3.12, this is a hard error, while 3.11 produces a deprecation warning. The correct syntax uses
\\-.I assume the
# noqacomments were suppressing a static check which identified this as a problem.This PR doesn't cause any change in behavior, except for suppressing the
SyntaxError/Warninggenerated by the invalid string literal.Todos