{{ message }}
[3.10] bpo-46615: Don't crash when set operations mutate the sets (GH-31120)#31284
Merged
miss-islington merged 1 commit intoFeb 11, 2022
Merged
Conversation
Contributor
Sorry, something went wrong.
Contributor
Author
|
@sweeneyde: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
Contributor
Author
|
@sweeneyde: Status check is done, and it's a success ✅ . |
Sorry, something went wrong.
serhiy-storchaka
approved these changes
Feb 11, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
5 participants
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
Ensure strong references are acquired whenever using
set_next(). Added randomized test cases for__eq__methods that sometimes mutate sets when called.(cherry picked from commit 4a66615)
Co-authored-by: Dennis Sweeney 36520290+sweeneyde@users.noreply.github.com
https://bugs.python.org/issue46615