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 ncoghlan
Recipients grahamd, ncoghlan, tim.peters
Date 2013-09-22.11:23:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379849037.26.0.0523888964286.issue19070@psf.upfronthosting.co.za>
In-reply-to
Content
Ouch :P

Perhaps the least-incompatible fix would be to switch to returning the proxy if the object returned is the proxied object (which would do the right thing for proxies to mutable objects), while preserving the current behaviour when the in-place operation returns a new object?

That behaviour is still somewhat broken, but there's no obviously non-broken behaviour in that case, and this broadly preserves compatibility with the status quo.
History
Date User Action Args
2013-09-22 11:23:57ncoghlansetrecipients: + ncoghlan, tim.peters, grahamd
2013-09-22 11:23:57ncoghlansetmessageid: <1379849037.26.0.0523888964286.issue19070@psf.upfronthosting.co.za>
2013-09-22 11:23:57ncoghlanlinkissue19070 messages
2013-09-22 11:23:56ncoghlancreate