[issue31973] Incomplete DeprecationWarning for async/await keywords

Barry A. Warsaw added the comment: My sense is that we will never fix this, so closing as Won't Fix. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue31973] Incomplete DeprecationWarning for async/await keywords

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue31973] Incomplete DeprecationWarning for async/await keywords

Sorin Sbarnea added the comment: I agree that this deprecation approach is not very helpful because it does not indicate a recommended way to fix. Yep, we all know that we will be forced to rename these parameters/variables everywhere and likely break few APIs due to

[issue31973] Incomplete DeprecationWarning for async/await keywords

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue31973] Incomplete DeprecationWarning for async/await keywords

Change by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31973] Incomplete DeprecationWarning for async/await keywords

New submission from Barry A. Warsaw : Issue bpo-26182 added DeprecationWarnings for "import async" and "import await" since both of those pseudo-keywords were to become actual reserved keywords in Python 3.7. This latter has now happened, but the fix in bpo-26182 is