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 pstch
Recipients The Compiler, cjw296, michael.foord, ncoghlan, pstch, yselivanov
Date 2016-08-21.06:30:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471761059.24.0.863543993535.issue25532@psf.upfronthosting.co.za>
In-reply-to
Content
You are right, the fix would be better suited in `unwrap`. 

But, still, shouldn't any `__getattr__` implementation take care of not returning, for the `__wrapped__` attribute, a dynamic wrapper that provides the same attribute ? `__wrapped__` is commonly resolved to the innermost value without `__wrapped__`, which in this case never happens.

This would also avoid problems with introspection tools that resolve `__wrapped__` without the help of `unwrap` (before Python 3.4 IIRC).
History
Date User Action Args
2016-08-21 06:30:59pstchsetrecipients: + pstch, ncoghlan, cjw296, michael.foord, yselivanov, The Compiler
2016-08-21 06:30:59pstchsetmessageid: <1471761059.24.0.863543993535.issue25532@psf.upfronthosting.co.za>
2016-08-21 06:30:59pstchlinkissue25532 messages
2016-08-21 06:30:59pstchcreate