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 grahamd, ncoghlan, shishkander, tim.peters
Date 2013-10-07.10:06:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381140382.1.0.551013557053.issue19070@psf.upfronthosting.co.za>
In-reply-to
Content
The proxy is intended as a wrapper around an object, it is not intended to merge in some way with the wrapped object. The wrapped object shouldn't really ever be aware that it was being accessed via a proxy. Thus the expectation that the 'self' attribute of the methods of the wrapper object would actually be the proxy object is a strange one.

Can you explain why you need it to behave the way you are expecting? Also specifically indicate what requirement you have for needing the reference to the wrapped object to be a weakref?

Almost sounds a bit like you may be trying to use weakref.proxy in a way not intended.

It is technically possible to write an object proxy which would work how you are expecting, but the Python standard library doesn't provide an object proxy implementation to base such a thing on.
History
Date User Action Args
2013-10-07 10:06:22grahamdsetrecipients: + grahamd, tim.peters, ncoghlan, shishkander
2013-10-07 10:06:22grahamdsetmessageid: <1381140382.1.0.551013557053.issue19070@psf.upfronthosting.co.za>
2013-10-07 10:06:22grahamdlinkissue19070 messages
2013-10-07 10:06:21grahamdcreate