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 rhettinger
Recipients amaury.forgeotdarc, arigo, corona10, erlendaasland, ghaering, iritkatriel, jcea, lkraav, pablogsal, pitrou, pxd, rhettinger, vstinner
Date 2021-02-22.03:33:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1613964781.51.0.2269814799.issue15108@roundup.psfhosted.org>
In-reply-to
Content
Unless there is a simple, reliable, cheap, and universal solution at hand, consider closing this.  Given how long PyTuple_New() has exist, it doesn't seem to be much of a problem in the real world.

Historically, we punted on "crashers" involving either gc.get_referrers or byte code hacks.  Both of those reach inside Python's black box, allowing disruption of otherwise sensible invariants.
History
Date User Action Args
2021-02-22 03:33:01rhettingersetrecipients: + rhettinger, arigo, jcea, ghaering, amaury.forgeotdarc, pitrou, vstinner, lkraav, pxd, corona10, pablogsal, erlendaasland, iritkatriel
2021-02-22 03:33:01rhettingersetmessageid: <1613964781.51.0.2269814799.issue15108@roundup.psfhosted.org>
2021-02-22 03:33:01rhettingerlinkissue15108 messages
2021-02-22 03:33:01rhettingercreate