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 SilentGhost, Tim.Graham, brett.cannon, eric.snow, larry, ncoghlan, ned.deily, python-dev, r.david.murray, ryan.petrello, serhiy.storchaka, yselivanov
Date 2017-11-30.18:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'm not saying we remove getfullargspec() **right now**, just that we don't keep it around long-term as it simply can't evolve to keep up with how rich our parameter support is today and might become in the future. And that's why, for me, the deprecation was enough to signal, "this code is here for now and you can use it, but you really need to be aware of some issues that are leading to it being removed". Now obviously you prefer the doc approach for this, Nick, and that's fine since this is quickly devolving into "agree to disagree" as while "there are plenty of other standard library APIs that we keep around primarily for backwards compatibility reasons", I personally would say we should be prepared to deprecate them for Python 4 (which is what I'm talking about here, not e.g. 3.8).
Date User Action Args
2017-11-30 18:39:31brett.cannonsetrecipients: + brett.cannon, ncoghlan, larry, ned.deily, r.david.murray, SilentGhost, python-dev, eric.snow, serhiy.storchaka, yselivanov, Tim.Graham, ryan.petrello
2017-11-30 18:39:31brett.cannonsetmessageid: <>
2017-11-30 18:39:31brett.cannonlinkissue27172 messages
2017-11-30 18:39:31brett.cannoncreate