-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
gh-136517: Print uncollectable objects if DEBUG_UNCOLLECTABLE mode was set #136518
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-136517: Print uncollectable objects if DEBUG_UNCOLLECTABLE mode was set #136518
Conversation
Misc/NEWS.d/next/Core_and_Builtins/2025-07-10-23-23-50.gh-issue-136517._NHJyv.rst
Outdated
Show resolved
Hide resolved
…e-136517._NHJyv.rst Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
@pablogsal @nascheme It is ready to review. Please take a look! |
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.
LGTM good catch!
Thanks @sergey-miryanov for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…ode was set (pythonGH-136518) (cherry picked from commit c560df9) Co-authored-by: Sergey Miryanov <sergey.miryanov@gmail.com>
GH-136522 is a backport of this pull request to the 3.14 branch. |
Thanks everyone! |
There was a typo, and uncollectable objects printed only if DEBUG_COLLECTABLE mode is set.
Affected main and 3.14 (183b020)
cpython/Python/gc.c
Lines 1783 to 1787 in 59acdba