On Nov 7, 2017, at 13:34, Jakub Wilk <jw...@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
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
