-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
gh-108927: Fix test_import + test_importlib + test_unittest problem #108929
Conversation
@@ -6,7 +6,6 @@ | |||
import pickle | |||
from test import support | |||
from test.support import import_helper | |||
import test.test_importlib.util |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious why such standard import triggers a bug. Maybe give a try to test.bisect_cmd to isolate exactly which tests are the bare minimum to trigger it.
#108952 is a more proper fix, but I think it needs a bit more discussion. I'm going to land this so the 3.12.0rc2 release process is a bit more clean, but we should still try to solve the more structural problem. |
…blem (pythonGH-108929) (cherry picked from commit 3f89b25) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
GH-108954 is a backport of this pull request to the 3.12 branch. |
Please can we backport this to 3.11 as well? I'm seeing this issue in 3.11.6 and earlier. |
GH-110347 is a backport of this pull request to the 3.11 branch. |
…blem (pythonGH-108929) (cherry picked from commit 3f89b25) Co-authored-by: Nikita Sobolev <mail@sobolevn.me>
Done. It was forgotten, tests should be backported to all bugfix branches. |
After:
This is more like "hidding things under the carpet" and not a "proper fix", I think.
But, it should be enough to unblock the release.