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 stw
Recipients pitrou, stw
Date 2012-05-23.16:22:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337790159.95.0.721831498272.issue14775@psf.upfronthosting.co.za>
In-reply-to
Content
> I had a thought about untracking tuples. If a tuple contains only
> immutable objects (atomics and tuples of atomics etc), then it should
> be untracked. Once untracked, it will never need to be tracked again
> since the tuple is immutable. If a tuple contains mutable objects, it
> will always need to be tracked.

> True. However, some tuples may be in an unfinished state (they are 
> being built up internally and a GC collection occurred in the middle).

So the tuple is linked-in to the garbage collection list before its contents are constructed?

> I was wondering whether it is possible to determine whether a tuple
> needs to be tracked or not the first time it appears in generation 0 -
> tuples in older generations would then not need to be considered.

> I'm not sure that would make much of a difference in practice. Most
> tuples are very short, so checking them for untracking should be
> reasonably fast.

Could tuples not be untracked at creation time then, or do not enough survive to gc to make this worthwhile?
History
Date User Action Args
2012-05-23 16:22:40stwsetrecipients: + stw, pitrou
2012-05-23 16:22:39stwsetmessageid: <1337790159.95.0.721831498272.issue14775@psf.upfronthosting.co.za>
2012-05-23 16:22:39stwlinkissue14775 messages
2012-05-23 16:22:39stwcreate