-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
Py_NewInterpreter causes bogus fatal error along the failure path #90128
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
Comments
The failure cleanup of |
@hackhaslam can you provide a test to reproduce what you are reporting? |
I can't remember any more what I did to cause |
We've moved to within since then and the CLA process has changed. Do you want to try again? Also, the PR would need a unit test so we need to know how to reproduce the bug. |
I don't remember what I was doing to get into the failure path. I can see a few different cases (lines with |
Ok, thanks. I'll close it then. |
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: