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 scoder
Recipients eelizondo, scoder
Date 2019-01-25.08:26:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It seems right that a heap allocate object owns a reference to its (non-static) type. But the mere fact that you had to adapt stdlib code makes it obvious that this will also break existing user code out there. And such breakage is very likely to remain undetected for a while, since leaking types is unlikely to have a big enough memory impact in most application to be easily detected.

This is a tough call. Any ideas for reducing the chance of breakage or increasing the chance of detecting it in user code would help.
Date User Action Args
2019-01-25 08:26:58scodersetrecipients: + scoder, eelizondo
2019-01-25 08:26:56scodersetmessageid: <>
2019-01-25 08:26:56scoderlinkissue35810 messages
2019-01-25 08:26:56scodercreate