Open
Conversation
Signed-off-by: Aryan Yadav <141573833+aryan0931@users.noreply.github.com>
|
Huh? Why would we not simply quote the backslashes? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes: #78
Description
This PR updates two regular expression strings in
Calculate.activity/astparser.pyto use Python raw string notation (r'').This prevents unintended escape sequence issues and resolves warnings raised by the Python interpreter when running the script.
Why this change?
Using raw strings in regular expressions ensures that backslashes (
\) are treated literally, avoiding misinterpretation as Python escape sequences.This is especially important for patterns like
\.(literal dot) or\d, etc.Testing