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 ysj.ray
Recipients andrea.corbellini, belopolsky, georg.brandl, kristjan.jonsson, pitrou, ysj.ray
Date 2010-07-30.09:09:15
SpamBayes Score 0.00069099717
Marked as misclassified No
Message-id <1280480957.6.0.278737763531.issue9417@psf.upfronthosting.co.za>
In-reply-to
Content
> However here's a proposed solution:

* for the __mro__: instead of using a tuple, use a new object that inherits from it. This new object should use weak reference for the first item and should return the real object (if available) only in __getitem__().

* __objclass__ can should become a property based on weak references.



I'm afraid doing so could cause some public C API change. For example, the PyDescr_TYPE, if we implemented all the Descriptor object's d_type(that is the __objclass__ of all types of descriptors) based on weakref, we could have all the callers who call the descriptor functions to check weather the weak-referented class object has gone away.
History
Date User Action Args
2010-07-30 09:09:17ysj.raysetrecipients: + ysj.ray, georg.brandl, belopolsky, pitrou, kristjan.jonsson, andrea.corbellini
2010-07-30 09:09:17ysj.raysetmessageid: <1280480957.6.0.278737763531.issue9417@psf.upfronthosting.co.za>
2010-07-30 09:09:16ysj.raylinkissue9417 messages
2010-07-30 09:09:15ysj.raycreate