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 mdk
Recipients abarry, mdk, serhiy.storchaka, sjpalt
Date 2016-12-04.22:51:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Problem looks mainly due to the __setattr__ done on a different type than the getattr, and the cache of PyType_Lookup:

 - type_setattro will be called with Foo, "x", and the value to set
 - type_getattro will be called with FooProxy, "x"

The timeline (with my is:

 - type_setattro is called on Foo for attr "x" with the instance of Bar
 - type_getattro is called on FooProxy for attr "x" (the `proxy.x` line)
     During this type_getattro, the instance of Bar is cached in PyType_Lookup for (FooProxy, "x")
 - type_setattro is called on Foo for attr "x" with the value 0
     During this call, insertdict will legitimately call DECREF on the Bar instance, which is deleted
 - type_getattro is called on FooProxy with attr "x" for the print()
     During this call, PyType_Lookup will cache hit for (FooProxy, x) with the old reference to the instance of Bar
Date User Action Args
2016-12-04 22:51:04mdksetrecipients: + mdk, serhiy.storchaka, abarry, sjpalt
2016-12-04 22:51:04mdksetmessageid: <>
2016-12-04 22:51:04mdklinkissue28866 messages
2016-12-04 22:51:04mdkcreate