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 ofey404
Recipients larry, ofey404, ping, yselivanov
Date 2022-02-24.02:50:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thank you Larry.  It can never be too careful to deal with language issues!

> why the code behaves like this--is this behavior a genuine bug, or is it actually a bugfix for some worse behavior?

In my view, there's rather an concept needing clarify, than a genuine bug.  I look into the file blame, and it shows the processing order around `follow_wrapper_chains` might be carefully arranged...

- The `follow_wrapper_chains` functionality is added in issue 13266:
- When `signature()` first implemented, `__wrapped__` is handled then `partial`, this order never changed.
   - Issue #15008: Implement PEP 362 "Signature Objects":

> will fixing the bug cause problems for Python users? and if so, can we still fix the bug while mitigating the damage to people who are unfortunately depending on the bug?

It's really a heavy responsibility!  Slow down is right... A clear explaination and plan should be constructed before any action is taken.

So I may study PEP 362 to get some context, about why the code is this way.  And I'm wondering what else can I do?
Date User Action Args
2022-02-24 02:50:47ofey404setrecipients: + ofey404, ping, larry, yselivanov
2022-02-24 02:50:47ofey404setmessageid: <>
2022-02-24 02:50:47ofey404linkissue46761 messages
2022-02-24 02:50:47ofey404create