Message111961
This is an unwanted an unexpected behavior, so this is a bug by definition. If it's not easy to fix, it's a different matter.
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. |
|
Date |
User |
Action |
Args |
2010-07-29 16:32:55 | andrea.corbellini | set | recipients:
+ andrea.corbellini, georg.brandl, pitrou, kristjan.jonsson, ysj.ray |
2010-07-29 16:32:55 | andrea.corbellini | set | messageid: <1280421175.79.0.0974523388682.issue9417@psf.upfronthosting.co.za> |
2010-07-29 16:32:53 | andrea.corbellini | link | issue9417 messages |
2010-07-29 16:32:53 | andrea.corbellini | create | |
|