Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix regex escape warning in _coverage.py by using raw string#28195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
harsh-suman5 wants to merge2 commits intoopencv:4.x
base:4.x
Choose a base branch
Loading
fromharsh-suman5:fix-coverage-regex

Conversation

@harsh-suman5
Copy link

while i am running '_coverage.py' I noticed there is a syntax warning:"." It is an invalid escape sequence
The regex was written as a normal string with '.' which is not valid escape in string literals and give problems and error in a new python versions.
To fix this switch to raw string(r'cv2?.\w+') which can passes the backslashes directly to the regex engine. This removes the warning and keeps the code and pattern working properly.

This is a small fix but important for future compatibilities.

@harsh-suman5
Copy link
Author

Hello opencv admins, I saw that some of the buildbot checks are throwing “exception” and the dashboard says the service is in a degraded state.
My change is really small — it only updates _coverage.py to use a raw string so the regex doesn’t trigger a SyntaxWarning. It doesn’t touch any core OpenCV functionality.
Looks like the exceptions are more about the CI system than this fix, but just wanted to point it out. Happy to adjust if needed!

@harsh-suman5
Copy link
Author

Hi, all core CI checks have passed successfully (23/26).
The only failing job is on Windows (x86) and seems unrelated to this PR — it failed during the cleanup step with an EBUSY error (locked build folder).
The code changes themselves are clean and validated.
Could you please approve or re-run the workflow so the latest commit can be verified? Thanks!

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@harsh-suman5

[8]ページ先頭

©2009-2025 Movatter.jp