fix: use raw string for regex backreference in message_composer.py#922
Merged
volodkindv merged 1 commit intoJul 10, 2026
Merged
Conversation
Fixes SyntaxWarning 'invalid escape sequence \g' on Python 3.12+. \g<0> is a valid regex backreference but Python warned about raw \g before the engine got it. Changed to r-string — no behavior change.
volodkindv
force-pushed
the
feature/fix-regex-escape-warning
branch
from
90049fb to
63b3fe7
Compare
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
1 participant
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 SyntaxWarning 'invalid escape sequence \g' on Python 3.12+. \g<0> is a valid regex backreference but Python warned about raw \g before the engine got it. Changed to r-string — no behavior change.