bpo-30406: Make async and await proper keywords#1669
Conversation
|
I might need some time to fix the test failures. |
Sorry, something went wrong.
|
Alright, But in general it looks like a nice start. |
Sorry, something went wrong.
|
Overall looks good. I'll make a detailed review in a few days. |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
https://docs.python.org/dev/reference/grammar.html should also be updated, no?
Sorry, something went wrong.
|
grammar.html just directly includes Grammar/Grammar, so it shouldn't require further changes. |
Sorry, something went wrong.
|
@JelleZijlstra you mind also removing 'asyncio.async' as well as that thing might cause an SyntaxError. |
Sorry, something went wrong.
|
Thanks for the clarification :-) I let Yury review the change. He knows the
parser much better than me!
|
Sorry, something went wrong.
|
@AraHaan it's currently implemented as something like |
Sorry, something went wrong.
|
Ok |
Sorry, something went wrong.
|
I'll merge this when I return from my vacation in 11 days. Thank you for keeping the pr up to date! |
Sorry, something went wrong.
1st1
left a comment
There was a problem hiding this comment.
Overall looks good. Could you please rename it once again and add a news entry with blurb?
Sorry, something went wrong.
|
s/rename/rebase |
Sorry, something went wrong.
f2838a0 to
6562616
Compare
July 21, 2017 05:04
|
Just rebased from current master and added a news entry using blurb. |
Sorry, something went wrong.
|
The AppVeyor failure is in test_idle and looks unrelated to this PR. |
Sorry, something went wrong.
Rebase again and it should be fine. |
Sorry, something went wrong.
16949e3 to
36ea452
Compare
July 21, 2017 15:52
1st1
left a comment
There was a problem hiding this comment.
Playing with the code right now. One of the things you also need to do is to cleanup forbidden_name() function in Python/ast.c.
Sorry, something went wrong.
|
Ping? I plan to work on this myself if this isn't resolved soon. |
Sorry, something went wrong.
|
I was unable to resolve the issue I mentioned in #1669 (comment). I can push out the other fixes though and take another look within the next few days to see if I can get it working. |
Sorry, something went wrong.
Interesting. I'll take a look at that too. |
Sorry, something went wrong.
2ed73d1 to
78ddbde
Compare
October 6, 2017 02:11
|
Just rebased and adjusted the lib2to3 grammar changes to make local tests pass. |
Sorry, something went wrong.
@1st1 requested this in python#1669 (comment).
|
@JelleZijlstra This change is incorrect in lib2to3. That library's grammar is explicitly kept in a way that is able to parse all code valid for Python 2 - Python 3.7. With your change we lost the ability to read valid Python 2 - Python 3.6 code that uses |
Sorry, something went wrong.
|
Hm, I'm not sure what options we have here. Any suggestions? About the only one that I have is to undo the change for lib2to3 entirely (but keeping the rest of the changes). |
Sorry, something went wrong.
|
Yes, this is what I'm inclined to do. Revert the lib2to3 part. |
Sorry, something went wrong.
|
If I recall correctly I made changes to lib2to3 because some test was failing otherwise, so it might not be as simple as just reverting parts of this PR. I can spend some time looking into this later today. |
Sorry, something went wrong.
This reverts commit ac31770. (Reverts only the lib2to3 part.)
This reverts commit ac31770. (Reverts only the lib2to3 part.)
…" (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>
pythonGH-6143) This reverts commit ac31770. (Reverts only the lib2to3 part.)
https://bugs.python.org/issue30406