<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 28, 2015 at 4:55 PM, Ethan Furman <span dir="ltr"><<a href="mailto:ethan@stoneleaf.us" target="_blank">ethan@stoneleaf.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 04/28, Yury Selivanov wrote:<br>
<br>
</span><span class="">>>> This limitation will go away as soon as ``async`` and ``await`` ate<br>
>>> proper keywords. Or if it's decided to use a future import for this<br>
>>> PEP.<br>
<br>
</span>`async` and `await` need to be proper keywords, and __future__ imports<br>
is how we do that (see, e.g., PEP 355 and and PEP 343)<br clear="all"></blockquote><div><br></div><div>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).<br></div></div><br>-- <br><div class="gmail_signature">--Guido van Rossum (<a href="http://python.org/~guido" target="_blank">python.org/~guido</a>)</div>
</div></div>