29 Apr
2015
29 Apr
'15
12:04 a.m.
On Tue, Apr 28, 2015 at 4:55 PM, Ethan Furman
On 04/28, Yury Selivanov wrote:
This limitation will go away as soon as ``async`` and ``await`` ate proper keywords. Or if it's decided to use a future import for this PEP.
`async` and `await` need to be proper keywords, and __future__ imports is how we do that (see, e.g., PEP 355 and and PEP 343)
You could at least provide an explanation about how the current proposal falls short. What code will break? There's a cost to __future__ imports too. The current proposal is a pretty clever hack -- and we've done similar hacks in the past (last I remember when "import ... as ..." was introduced but we didn't want to make 'as' a keyword right away). -- --Guido van Rossum (python.org/~guido)