bpo-46920: Remove an old, elementtree-specific leak detector - #31811
Merged
ericvsmith merged 1 commit intoMar 11, 2022
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
vstinner
approved these changes
Mar 11, 2022
vstinner
left a comment
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
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
Add this suggestion to a batch that can be applied as a single commit.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.Add this suggestion to a batch that can be applied as a single commit.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.Suggestion cannot be applied right now. Please check back later.
Currently, CPython has a universal refleak detector that reports on interpreter termination. As a result, no commented out elementtree-specific detector is required, especially when it prints into stdout for each ElementObject creation and destruction.
This PR is separated from a large, umbrella GH-31681 to simplify review.
https://bugs.python.org/issue46920