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-22.13:06:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337691986.92.0.540279082968.issue14775@psf.upfronthosting.co.za>
In-reply-to
Content
> Probably because memoization itself uses a dict.

Right, but as far as I can tell it's not the memo dict that keeps being tracked/untracked. Rather, it's the dict that is being unpickled.

Anyway, I suppose the point is that the issue of whether an object is tracked/untracked is not solely determined by its type:

1. All containers are tracked by default.

2. Tuples can only become untracked after a generation 0 gc pass.

3. With the new patch, dicts can only become untracked after a generation 2 gc pass.

4. Also, am I right in thinking that whether a container gets untracked or not depends not only on its contents, but also on the order of the objects in the gc list? That is, all of the contents of a container must get untracked before the container is considered.
History
Date User Action Args
2012-05-22 13:06:27stwsetrecipients: + stw, pitrou
2012-05-22 13:06:26stwsetmessageid: <1337691986.92.0.540279082968.issue14775@psf.upfronthosting.co.za>
2012-05-22 13:06:26stwlinkissue14775 messages
2012-05-22 13:06:26stwcreate