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 zzzeek
Recipients brett.cannon, hroncok, lukasz.langa, ncoghlan, pablogsal, serhiy.storchaka, steve.dower, vstinner, zzzeek
Date 2019-05-17.01:55:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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 agree that the reason we have these deprecation warnings is so that we do get notified and we do fix them.  I think Signature is tough here because it is so different from how getfullargspec() worked which makes it difficult to port towards, and its very long and complicated invocation steps, with many loops, function and method calls, object creation overhead, none of which existed in Python 3.3's 20 line getfullargspec() implementation, is making me very hesitant to switch to it and I'm continuing to consider just writing my own thing that keeps the overhead as low as possible; but I will run timing tests on all versions of things before I do anything like that.
Date User Action Args
2019-05-17 01:55:53zzzeeksetrecipients: + zzzeek, brett.cannon, ncoghlan, vstinner, lukasz.langa, serhiy.storchaka, steve.dower, hroncok, pablogsal
2019-05-17 01:55:53zzzeeksetmessageid: <>
2019-05-17 01:55:53zzzeeklinkissue36751 messages
2019-05-17 01:55:53zzzeekcreate