[Python-Dev] Proposal: go back to enabling DeprecationWarning by default
Barry Warsaw
barry at python.org
Tue Nov 7 18:16:28 EST 2017
On Nov 7, 2017, at 13:34, Jakub Wilk <jwilk at jwilk.net> wrote:
> "import async" would indeed cause deprecation warning, but that's not what ldap3 does. The only uses of the now-keyword "async" in their codebase are like this:
>
> from ..strategy.async import AsyncStrategy
> from .async import AsyncStrategy
>
> These do not provoke deprecation warnings from Python 3.6. (They probably should!)
>
> I'm afraid that showing deprecation warnings by default wouldn't have helped in this particular case.
Oh gosh, I should have tried that instead of assuming it would generate the same warning. Yes, that’s definitely a bug. I wonder if we should push back making async/await reserved words until Python 3.8?
https://bugs.python.org/issue31973
Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171107/2e5fcf56/attachment-0001.sig>
More information about the Python-Dev
mailing list