Message342296
> 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:26 | vstinner | set | recipients:
+ vstinner, brett.cannon, ncoghlan, lukasz.langa, serhiy.storchaka, steve.dower, hroncok, pablogsal |
2019-05-13 09:28:26 | vstinner | set | messageid: <1557739706.91.0.648506624871.issue36751@roundup.psfhosted.org> |
2019-05-13 09:28:26 | vstinner | link | issue36751 messages |
2019-05-13 09:28:25 | vstinner | create | |
|