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 michael.foord, ncoghlan, rhettinger
Date 2013-03-19.17:44:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There's an interesting backwards compatibility challenge here. We definitely need to fix the misbehaviour, since it can lead to some pretty serious bugs in user code when attempting to bypass the LRU cache decorator if the wrapped function itself had a __wrapped__ attribute.

However, Michael tells me that at least some third party clients of the introspection tools assumed the "__wrapped__ points to the bottom of the wrapper stack" behaviour was intentional rather than just me screwing up the implementation.

The existing docs for update_wrapper are unfortunately ambiguous because they use the term "original function" instead of "wrapped function".
Date User Action Args
2013-03-19 17:44:45ncoghlansetrecipients: + ncoghlan, rhettinger, michael.foord
2013-03-19 17:44:45ncoghlansetmessageid: <>
2013-03-19 17:44:45ncoghlanlinkissue17482 messages
2013-03-19 17:44:45ncoghlancreate