(original) (raw)

Hi Wolfgang,

On 2015-04-23 8:27 AM, Wolfgang Langner wrote:

On Thu, Apr 23, 2015 at 12:35 PM, Paul Sokolovsky <pmiscml@gmail.com> wrote:

Hello,

On Thu, 23 Apr 2015 12🔞51 +0300
Andrew Svetlov <andrew.svetlov@gmail.com> wrote:

\[\]

3.
async with and async for
Bead idea, we clutter the language even more and it is one more
thing every newbie could do wrong.
for x in y:
result = await f()
is enough, every 'async' framework lived without it over years.

async for i in iterable:
pass

is not equal for

for fut in iterable:
i = yield from fut

But people who used Twisted all their life don't know that! They just
know that "async for" is not needed and bad.

I don't think it is bad nor not needed, but the syntax is not beautiful and
for the 90% not doing async stuff irritating and one more thing to learn
and do right/wrong.

There is no way to do things wrong in PEP 492\. An object
either has \_\_aiter\_\_ or it will be rejected by async for.
An object either has \_\_aenter\_\_ or it will be rejected by
async with.

transaction = yield from connection.transaction()
try:
...
except:
yield from transaction.rollback()
else:
yield from transaction.commit()

is certainly more irritating than

async with connection.transcation():
...