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-92112: Fix crash triggered by an evil custom mro()
#92113
Conversation
|
If you want to schedule another build, you need to add the " |
|
Thanks @izbyshev for the PR, and @JelleZijlstra for merging it |
|
Sorry, @izbyshev and @JelleZijlstra, I could not cleanly backport this to |
|
Sorry @izbyshev and @JelleZijlstra, I had trouble checking out the |
…ythonGH-92113). (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <[email protected]>
|
GH-92370 is a backport of this pull request to the 3.10 branch. |
…ythonGH-92113). (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <[email protected]>
|
GH-92372 is a backport of this pull request to the 3.9 branch. |
) (#92370) (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <[email protected]>
|
Ooohhhh you fixed it! Thanks @izbyshev! It was the following item on my todo-list, and woosh, already fixed! Out of curiosity, how did you discovered the issue? |
|
You're welcome, @JulienPalard :)
Nothing smart, unfortunately. I was trying to investigate a couple of mysterious non-reproducible Python crashes on a CI box at work, which occurred in |
…ythonGH-92113) (pythonGH-92372) (cherry picked from commit 85354ed) Co-authored-by: Alexey Izbyshev <[email protected]>
No description provided.