This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients pablogsal
Date 2019-02-17.20:20:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550434835.07.0.108252572436.issue36016@roundup.psfhosted.org>
In-reply-to
Content
gc.get_objects() return all the objects tracked by the garbage collector. This is useful, but right now there is no way of knowing in which generation each object is currently on. This information can be beneficial to understand better the state of the garbage collector in a particular moment in time. 

This will allow knowing what are the oldest object tracked by the collector, gathering more fine-grained statistics about how generations are filled, better debugging and better insights about the internal structure of the generations.

To allow this, I propose a new optional parameter to gc.get_objects, allowing the user to specify the generation to get the objects from.
History
Date User Action Args
2019-02-17 20:20:35pablogsalsetrecipients: + pablogsal
2019-02-17 20:20:35pablogsalsetmessageid: <1550434835.07.0.108252572436.issue36016@roundup.psfhosted.org>
2019-02-17 20:20:35pablogsallinkissue36016 messages
2019-02-17 20:20:34pablogsalcreate