Skip to content

Fix invalid regex escape warnings#462

Draft
Mirochill wants to merge 1 commit into
ELELAB:mainfrom
Mirochill:fix-391-invalid-escapes
Draft

Fix invalid regex escape warnings#462
Mirochill wants to merge 1 commit into
ELELAB:mainfrom
Mirochill:fix-391-invalid-escapes

Conversation

@Mirochill
Copy link
Copy Markdown

Summary:

  • Fixes Invalid escape sequence warnings #391.
  • Converts the four reported regex patterns in mavisp/modules.py to raw strings.
  • Preserves the existing regex behavior while avoiding Python invalid escape sequence warnings.

Validation:

  • git diff --check
  • Targeted rg check for the reported escaped patterns in mavisp/modules.py

Not run locally: test suite.

Use raw strings for the regular expressions reported in issue ELELAB#391 so Python no longer emits invalid escape sequence warnings while preserving the existing regex patterns.
@mtiberti
Copy link
Copy Markdown
Contributor

hi @Mirochill , thanks for your PRs. Look sensible at first sight.

Are you a human or a bot, and are these AI-generated code changes? Same for questions for #461

@Mirochill
Copy link
Copy Markdown
Author

Thanks for asking. Both #461 and #462 were prepared with AI assistance through this GitHub account, not by a project-side bot. The changes were kept limited to the reported issues, and I checked the final diffs for scope and provenance. I did not run local tests; I only did static diff review, and I do not see CI checks published for these branches. If AI-assisted contributions are not acceptable for this project, I can close the PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid escape sequence warnings

2 participants