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
unset PYTHON* environment variables when running tests #56610
Comments
"make test" calls Python with the -E option which ignore the PYTHON* I see 2 solutions to this problems:
I think that solution #2 is better. Fixing the tests can be done today, but the authors of future tests might not be aware of this issue. By fixing the Makefile we prevent this problem to occur again in the future. |
Here's a small patch to call regression tests without any environment variable defined. It's probably a good thing to run all the tests with a clean state, this way they are less likely to fail for mysterious external reasons. For example test_displayhook_unencodable was failing because I was overriding displayhook in my PYTHONSTARTUP file. On the other hand, some problems with environment variables might go unnoticed. But I don't think there's much risk. Note that test_distutils will fail with this patch if bpo-12420 is not taken care of beforehand. |
Can we have a formal patch review please as "make test" means nothing to me. |
Yes, this is the right fix. I'm closing this issue because it didn't get any activity since 3 years. If you are interested to add -E in tests, please open a new issue with a patch. empty_environment.diff is wrong, we should ignore PYTHON environement variables to have reliable tests. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: