-
-
Notifications
You must be signed in to change notification settings - Fork 440
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using regex in docs #1863
Comments
Thanks, that's poor testing on my part. It will work if you change it to:
I'll update the docs. |
nedbat
added a commit
that referenced
this issue
Sep 26, 2024
nedbat
added a commit
that referenced
this issue
Sep 26, 2024
Indeed it does, thanks Ned! |
I've updated the docs in commit 3e15cbe. |
This is now released as part of coverage 7.6.2. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the following code in my pyproject.toml, as documented:
When running
coverage report
, I receive the following traceback:Removing the line from the configuration fixes things.
I didn't have time to investigate very thoroughly (sorry!), but If I had to make a random guess, I'm guessing this regex gets concatenated with other(s) and the
(?s)
is no longer at the beginning, which is broken in Python 3.11+.To Reproduce
Unfortunately, this doesn't seem to be perfectly reproducible. While I can reproduce this now 100% of the time, when I first introduced the configuration, all seemed well. It was only (very) shortly after that this seemed to happen.
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:
coverage debug sys
is helpful. - 7.6.1pip freeze
is helpful. - see belowgit clone
,pip install
, and so on. Explain like we're five! - unsure what this depends on, butcoverage run -m pytest
followed bycoverage report
gives me the traceback. I run it like this to make sure pytest-cov or pytest-xdist are not the problemPackages
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Relevant configuration:
I saw that the code has changed a little in the master branch, so I tried that as well, but just got a slightly different traceback:
The text was updated successfully, but these errors were encountered: