10 Aug
2019
10 Aug
'19
7:01 a.m.
10.08.19 02:04, Gregory P. Smith пише:
I've merged the PR reverting the behavior in 3.8 and am doing the same in the master branch.
I was going to rebase it to master and go in normal backporting process if we decide that DeprecationWarning should be in master. I waited the end of the discussion.
Recall the nightmare caused by md5.py and sha.py DeprecationWarning's in 2.5... this would be similar.
It is very different because DeprecationWarning for md5.py and sha.py is emitted at runtime.