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 vstinner
Recipients brett.cannon, hroncok, lukasz.langa, ncoghlan, pablogsal, serhiy.storchaka, steve.dower, vstinner
Date 2019-05-13.09:28:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> And no, the undeprecation wasn't because of Python 2 (Py2 doesn't have getfullargspec() - it's a Py3 only API).

Python 3.8.0 is scheduled for: "3.8.0 final: Monday, 2019-10-21"

Something like 2 months before 2.7 end of support: 2019-12-31.

Does the "because of Python 2" still stand for Python 3.8?

A deprecating warning doesn't hurt: you are still able to run your code. Moreover, deprecating warnings are ignored by default (except in the __main__ module). I don't see what is the *practical* issue of deprecating getfullargspec().

getfullargspec() has to die sometimes, it's good to warn users, no :-)

Or is the *long term plan* to keep getfullargspec() forever?


I basically have no opinion on these questions. I'm more curious about the long term plan ;-)
Date User Action Args
2019-05-13 09:28:26vstinnersetrecipients: + vstinner, brett.cannon, ncoghlan, lukasz.langa, serhiy.storchaka, steve.dower, hroncok, pablogsal
2019-05-13 09:28:26vstinnersetmessageid: <>
2019-05-13 09:28:26vstinnerlinkissue36751 messages
2019-05-13 09:28:25vstinnercreate