You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/gvanrossum'closed_at=<Date2017-10-06.03:28:00.513>created_at=<Date2017-05-19.21:27:41.864>labels= ['interpreter-core', 'type-bug', '3.7']
title='async and await should be keywords in 3.7'updated_at=<Date2019-02-27.23:41:58.653>user='https://github.com/JelleZijlstra'
According to PEP-492, async and await should be full keywords in Python 3.7, but this hasn't been implemented yet. I have a patch ready that I'll submit as a PR soon.
According to PEP-492, async and await should have been deprecated in 3.5 and 3.6, but I don't think they have been :
await=1deff(async=True):
...
don't raise any deprecation warning in 3.6.
Since version 3.7 will break existing code with a SyntaxError, could it be possible to have something explicit in the SyntaxError message for these new keywords, for instance
SyntaxError : 'async' is a keyword
I don't speack C so I can't provide a patch, sorry.
New changeset f64aae4 by Łukasz Langa (Jelle Zijlstra) in branch 'master':
Revert "bpo-30406: Make async and await proper keywords (bpo-1669)" (GH-6143) f64aae4
Activity
JelleZijlstra commentedon May 19, 2017
According to PEP-492, async and await should be full keywords in Python 3.7, but this hasn't been implemented yet. I have a patch ready that I'll submit as a PR soon.
rhettinger commentedon May 20, 2017
+1 These words are here to stay.
That said, Guido needs to explicitly sign-off on any new language keywords.
gvanrossum commentedon May 20, 2017
Yes, I signed off on this when I approved that PEP.
On May 19, 2017 20:10, "Raymond Hettinger" <report@bugs.python.org> wrote:
vstinner commentedon May 20, 2017
It's time to remove Yury's hacks from the parser and get a sane syntax ;-) I agree to make async and await real keywords!
1st1 commentedon Oct 6, 2017
New changeset ac31770 by Yury Selivanov (Jelle Zijlstra) in branch 'master':
bpo-30406: Make async and await proper keywords (bpo-1669)
ac31770
1st1 commentedon Oct 6, 2017
Thanks a lot, Jelle!
PierreQuentel commentedon Nov 4, 2017
According to PEP-492, async and await should have been deprecated in 3.5 and 3.6, but I don't think they have been :
don't raise any deprecation warning in 3.6.
Since version 3.7 will break existing code with a SyntaxError, could it be possible to have something explicit in the SyntaxError message for these new keywords, for instance
SyntaxError : 'async' is a keyword
I don't speack C so I can't provide a patch, sorry.
vstinner commentedon Nov 6, 2017
python3 requires -Wd to display DeprecationWarning:
https://mail.python.org/pipermail/python-dev/2017-November/150149.html
Yury Selivanov: "We had PendingDeprecationWarning for async/await names in 3.5, and DeprecationWarning in 3.6."
ambv commentedon Mar 18, 2018
New changeset f64aae4 by Łukasz Langa (Jelle Zijlstra) in branch 'master':
Revert "bpo-30406: Make async and await proper keywords (bpo-1669)" (GH-6143)
f64aae4
miss-islington commentedon Mar 18, 2018
New changeset a90df50 by Miss Islington (bot) in branch '3.7':
Revert "bpo-30406: Make async and await proper keywords (GH-1669)" (GH-6143)
a90df50
gvanrossum commentedon Feb 27, 2019
Sadly if I get my way this will all be reverted -- see https://bugs.python.org/issue35975. I'm working on a PR.