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 terry.reedy
Recipients bup, miss-islington, taleinat, terry.reedy
Date 2020-04-04.20:37:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586032629.44.0.44066312897.issue38689@roundup.psfhosted.org>
In-reply-to
Content
get_argspec accesses the user object 3 times.  The first, ob.__call__ was already wrapped in try-except.  The second, signature(ob or ob.__call) is wrapped by this issue.  It also adds a new test based on Dan's example. The third is (ob or ob.__call__).__doc__.  I did not wrap this because I could not create an example for which this fails.  There seems to be some special casing of this special attribute so that its default is None.

I opened #40180 for the isinstance bug and #40181 for further get_argspec changes, in particular, removing the positional-only '/' note.
History
Date User Action Args
2020-04-04 20:37:09terry.reedysetrecipients: + terry.reedy, taleinat, bup, miss-islington
2020-04-04 20:37:09terry.reedysetmessageid: <1586032629.44.0.44066312897.issue38689@roundup.psfhosted.org>
2020-04-04 20:37:09terry.reedylinkissue38689 messages
2020-04-04 20:37:09terry.reedycreate