➜

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 grahamd
Recipients Claudiu.Popa, belopolsky, christian.heimes, eric.snow, eryksun, ethan.furman, grahamd, ionelmc, jedwards, llllllllll, r.david.murray, rhettinger, steven.daprano, terry.reedy
Date 2016-05-23.22:23:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464042222.33.0.672288291054.issue23990@psf.upfronthosting.co.za>
In-reply-to
Content 
If someone is going to try and do anything in the area of better proxy object support, I hope you will also look at all the work I have done on that before for wrapt (https://github.com/GrahamDumpleton/wrapt).

Two related issue this has already found are http://bugs.python.org/issue19072 and http://bugs.python.org/issue19070.

The wrapt package uses two separate proxy object types. A base ObjectProxy and a CallableObjectProxy because of the specific issue with how callable() works.
History
Date User Action Args
2016-05-23 22:23:42grahamdsetrecipients: + grahamd, rhettinger, terry.reedy, belopolsky, christian.heimes, ionelmc, steven.daprano, r.david.murray, Claudiu.Popa, ethan.furman, eric.snow, eryksun, llllllllll, jedwards
2016-05-23 22:23:42grahamdsetmessageid: <1464042222.33.0.672288291054.issue23990@psf.upfronthosting.co.za>
2016-05-23 22:23:42grahamdlinkissue23990 messages
2016-05-23 22:23:42grahamdcreate