-
-
Notifications
You must be signed in to change notification settings - Fork 442
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
coverage run
breaks PYTHONSAFEPATH
#1696
Comments
This was referenced Nov 13, 2023
Closed
#1700 is a pull request in progress to fix this. |
3 tasks
nedbat
pushed a commit
that referenced
this issue
Mar 22, 2025
Fix make test mostly work changes from code review changes from code review Fix lint error
nedbat
added a commit
that referenced
this issue
Mar 22, 2025
temp: fix lint errors from rebases docs: a note to ourselves about interpreting test failures test: one more safepath test fix: use sys.flags instead of reading the PYTHONSAFEPATH test: skip the test that show Windows gets PYTHONSAFEPATH wrong
Fixed in commit 32e8d79. |
thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When executing
coverage run -m ...
with the environment variablePYTHONSAFEPATH=1
set, the working directory appears insys.path
To Reproduce
Create the following two files
printpath.py
pyproject.toml
then run
Expected behavior
Both commands have the same output
The text was updated successfully, but these errors were encountered: