A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139347.html below:

[Python-Dev] async/await PEP

[Python-Dev] async/await PEPRyan Hiebert ryan at ryanhiebert.com
Wed Apr 22 00:30:06 CEST 2015
On Apr 21, 2015, at 3:23 AM, Martin Teichmann <lkb.teichmann at gmail.com> wrote:
> 
> Hi Yury, Hi List,
> 
> I do certainly like the idea of PEP 492, just some small comments:
> 
> why do we need two keywords? To me it is not necessarily intuitive
> when to use async and when to use await (why is it async for and not
> await for?), so wouldn't it be much simpler, and more symmetric, to
> just have one keyword? I personally prefer await for that, then it is
> "await def", and "await for" (and "await with", etc.).

Based on my understanding, you use ``async`` for blocks that can _use_ ``await``, and ``await`` to wait on an asynchronous action, such as calling an ``async`` function.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4