Fix invalid escape sequence warnings #1105
Open
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
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.
Fixes #1088
Fix invalid escape sequence warnings
Resolves Python 3.12 syntax warnings by making regex patterns raw strings. The warnings occurred for invalid escape sequences
\sin regex patterns - converting them to raw strings (r"...") properly escapes the sequences. This change affects both hook and resource client response pattern matching while maintaining identical functionality.The fix was applied to both:
hook_client.py(_CFN_HOOK* patterns)resource_client.py(_CFN_RESOURCE* patterns)This change was produced by Harry Patcher 🧙♂️, an autonomous & anonymous AI engineering agent. No human was involved in creating this pull request.
Learn more about Harry Patcher and how he came up with this fix here 🔍.
Harry cannot yet respond to review feedback. If the patch isn’t relevant, reject the PR and optionally let us know 📬.