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 brett.cannon
Recipients brett.cannon, hroncok, lukasz.langa, ncoghlan, pablogsal, serhiy.storchaka, steve.dower, vstinner, zzzeek
Date 2019-05-14.04:14:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
RE: "if a function continues to work correctly throughout the span of a Python X version, why does it need to be removed?"

In this case the argument is whether inspect.getfullargspec() works correctly in the face of positional-only parameters. There's also the usual maintenance burden like any other open source project has.

I know for me the thing is that getfullargspec() keeps getting patched up to support any changes we make to function signatures that aren't the smoothest or more accurate way to represent new semantics and so it hasn't been maintenance-free. And in the face of inspect.Signature which feels like a cleaner solution that is easier to improve upon as function signatures change it makes folks not want to keep putting work into the older functions.

I personally think we should at least document the deprecation of the functions to strongly encourage people to not use it in new code. I don't find the "Note that signature() and Signature Object provide the recommended API for callable introspection" message "loud" enough to get the message across.
Date User Action Args
2019-05-14 04:14:58brett.cannonsetrecipients: + brett.cannon, ncoghlan, vstinner, zzzeek, lukasz.langa, serhiy.storchaka, steve.dower, hroncok, pablogsal
2019-05-14 04:14:58brett.cannonsetmessageid: <>
2019-05-14 04:14:58brett.cannonlinkissue36751 messages
2019-05-14 04:14:57brett.cannoncreate