Message 299698 - Python tracker

➜

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	pitrou
Recipients	arigo, pitrou
Date	2017-08-03.11:20:49
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1501759250.2.0.149170481325.issue31105@psf.upfronthosting.co.za>
In-reply-to

Content
Yes, this is a potentially annoying limitation of the current scheme. Note that it's not obvious how to proceed for resizable objects such as lists. Should the list inform the GC of every internal resizing? May a list resize trigger a GC run? Also, a small container may keep alive a large non-GC object (think a 2-element list containing itself and a 1 GB bytestring). How will the GC know?

Yes, this is a potentially annoying limitation of the current scheme.

Note that it's not obvious how to proceed for resizable objects such as lists. Should the list inform the GC of every internal resizing? May a list resize trigger a GC run?

Also, a small container may keep alive a large non-GC object (think a 2-element list containing itself and a 1 GB bytestring).  How will the GC know?

History
Date	User	Action	Args
2017-08-03 11:20:50	pitrou	set	recipients: + pitrou, arigo
2017-08-03 11:20:50	pitrou	set	messageid: <1501759250.2.0.149170481325.issue31105@psf.upfronthosting.co.za>
2017-08-03 11:20:50	pitrou	link	issue31105 messages
2017-08-03 11:20:49	pitrou	create