[3.7] Revert "bpo-30406: Make async and await proper keywords" (GH-6143) by miss-islington · Pull Request #6145 · python/cpython
-
-
Notifications
You must be signed in to change notification settings - Fork 34.8k
Merged
Merged
Conversation
Contributor
This reverts commit ac31770.
(Reverts only the lib2to3 part.)
(cherry picked from commit f64aae4)
Co-authored-by: Jelle Zijlstra jelle.zijlstra@gmail.com
…" (pythonGH-6143) This reverts commit ac31770. (Reverts only the lib2to3 part.) (cherry picked from commit f64aae4) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
the-knights-who-say-ni
added
the
CLA signed
label
bedevere-bot
added
the
awaiting review
label
miss-islington
commented
Mar 18, 2018
miss-islington commented
Contributor Author
@JelleZijlstra and @1st1: Backport status check is done, and it's a failure ❌ .
Mariatta
commented
Mar 18, 2018
Mariatta commented
Member
cc @ambv
Mariatta
added
the
skip news
label
miss-islington
commented
Mar 18, 2018
miss-islington commented
Contributor Author
@JelleZijlstra and @1st1: Backport status check is done, and it's a success ✅ .
Mariatta
changed the title
[3.7] Revert "bpo-30406: Make async and await proper keywords (GH-1669)" (GH-6143)
[3.7] Revert "bpo-30406: Make async and await proper keywords" (GH-6143)
bedevere-bot
added
the
skip news
label
bedevere-bot
mentioned this pull request
miss-islington
commented
Mar 18, 2018
miss-islington commented
Contributor Author
@JelleZijlstra and @ambv: Backport status check is done, and it's a success ✅ .
1 similar comment
miss-islington
commented
Mar 18, 2018
miss-islington commented
Contributor Author
@JelleZijlstra and @ambv: Backport status check is done, and it's a success ✅ .
ambv
approved these changes
bedevere-bot
added
awaiting merge
and removed
awaiting review
labels
miss-islington
merged commit
a90df50
into
python:3.7
miss-islington
commented
Mar 18, 2018
miss-islington commented
Contributor Author
Thanks!
bedevere-bot
removed
the
awaiting merge
label
miss-islington
deleted the
backport-f64aae4-3.7
branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment