Message 172323 - 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.

In-reply-to
Author	asvetlov
Recipients	Robin.Schreiber, asvetlov
Date	2012年10月07日.17:08:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1349629739.35.0.714169644832.issue15650@psf.upfronthosting.co.za>

Content
From my perspective type object is referenced by module state. While module is present it's state hold all types exposed by module. After module has deleted it's state has cleaned up and types has gone away — thats look good to me. Instances of python classes (not extensions) hold ownership for it's class. I guess it done because python class can be constructed inside function and instance of this class should work after exit from that function like closure does. In case of extension modules enough to hold type reference into module state itself. Thoughts?

Content

From my perspective type object is referenced by module state.
While module is present it's state hold all types exposed by module.
After module has deleted it's state has cleaned up and types has gone away — thats look good to me.
Instances of python classes (not extensions) hold ownership for it's class. I guess it done because python class can be constructed inside function and instance of this class should work after exit from that function like closure does.
In case of extension modules enough to hold type reference into module state itself.
Thoughts?

History
Date	User	Action	Args
2012年10月07日 17:08:59	asvetlov	set	recipients: + asvetlov, Robin.Schreiber
2012年10月07日 17:08:59	asvetlov	set	messageid: <1349629739.35.0.714169644832.issue15650@psf.upfronthosting.co.za>
2012年10月07日 17:08:59	asvetlov	link	issue15650 messages
2012年10月07日 17:08:59	asvetlov	create

homepage