Issue 31973: Incomplete DeprecationWarning for async/await keywords (original) (raw)

Issue31973

Created on 2017-11-07 23:15 by barry, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg305798 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2017-11-07 23:15
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 incomplete. It does not trigger warnings on "from .async import foo". base/ __init__.py async.py good.py -----async.py x = 1 -----good.py from .async import x $ python3.6 -W error::DeprecationWarning -c "import base.good" $ python3.7 -c "import base.good" Traceback (most recent call last): File "", line 1, in File "/private/tmp/x1/base/good.py", line 1 from .async import x ^ SyntaxError: invalid syntax $ cd base $ python3.6 -W error::DeprecationWarning -c "import async" DeprecationWarning: 'async' and 'await' will become reserved keywords in Python 3.7
msg316910 - (view)	Author: Sorin Sbarnea (ssbarnea) *	Date: 2018-05-17 11:22
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 it. I am curious if there is any emerging pattern for new naming as I find really annoying if every python project using these keywords would endup picking different alternatives for their rename.
msg337891 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2019-03-14 00:31
My sense is that we will never fix this, so closing as Won't Fix.