Message 366403 - 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	carljm
Recipients	carljm, corona10, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, shihai1991, steve.dower, tim.peters, vstinner
Date	2020-04-14.17:12:20
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1586884341.11.0.844362428784.issue40255@roundup.psfhosted.org>
In-reply-to

Content
> An immortalized object will never start participating in reference counting again after it is immortalized. Well, "passed to an extension compiled with no-immortal headers" is an exception to this. But for the "not GC tracked but later becomes GC tracked" case, it will not re-enter reference counting, only the GC.

> An immortalized object will never start participating in reference counting again after it is immortalized.

Well, "passed to an extension compiled with no-immortal headers" is an exception to this.

But for the "not GC tracked but later becomes GC tracked" case, it will not re-enter reference counting, only the GC.

History
Date	User	Action	Args
2020-04-14 17:12:21	carljm	set	recipients: + carljm, tim.peters, nascheme, gregory.p.smith, pitrou, vstinner, steve.dower, corona10, pablogsal, eelizondo, shihai1991
2020-04-14 17:12:21	carljm	set	messageid: <1586884341.11.0.844362428784.issue40255@roundup.psfhosted.org>
2020-04-14 17:12:21	carljm	link	issue40255 messages
2020-04-14 17:12:20	carljm	create