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 pablogsal
Recipients brett.cannon, hroncok, lukasz.langa, ncoghlan, pablogsal, serhiy.storchaka, steve.dower, vstinner, zzzeek
Date 2019-05-16.20:07:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For now, I am going to proceed to merge PR13245 and un-deprecate getfullargspec().

Being said that I would want to remark that if test suites are broken when deprecation warnings are emitted that is (1) their own choice, (2) precisely to detect when some deprecation is happening. If we apply some version of this reasoning to everything the standard library will not be able to deprecate anything (not even raise deprecation warnings!). We are talking again and again that we have a lot of old things in the standard library but it seems that removing them is also a problem.

I want to make clear that I understand the arguments here and this is why I am going to merge PR13245 and I also apologize for any pain this may cause, but I also would ask people for empathy towards the standard library, Python and core developers.

Regarding PEP570, getfullargspec() will report positional-only arguments as regular arguments.
Date User Action Args
2019-05-16 20:07:33pablogsalsetrecipients: + pablogsal, brett.cannon, ncoghlan, vstinner, zzzeek, lukasz.langa, serhiy.storchaka, steve.dower, hroncok
2019-05-16 20:07:33pablogsalsetmessageid: <>
2019-05-16 20:07:33pablogsallinkissue36751 messages
2019-05-16 20:07:33pablogsalcreate