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 llllllllll
Recipients barry, eric.smith, eric.snow, llllllllll, rhettinger
Date 2015-04-27.13:13:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430140403.77.0.883111113369.issue23910@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think that I can cache the __call__ of the fget object because it might be an instance of a heaptype, and if someone changed the __class__ of the object in between calls to another heaptype that had a different __call__, you would still get the __call__ from the first type. I also don't know if this is supported behavior or just something that works by accident.

I read through PyObject_Call, and all the code is needed assuming we are not caching the tp_call value.
History
Date User Action Args
2015-04-27 13:13:23llllllllllsetrecipients: + llllllllll, barry, rhettinger, eric.smith, eric.snow
2015-04-27 13:13:23llllllllllsetmessageid: <1430140403.77.0.883111113369.issue23910@psf.upfronthosting.co.za>
2015-04-27 13:13:23lllllllllllinkissue23910 messages
2015-04-27 13:13:23llllllllllcreate