homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients asvetlov, ericvw, gvanrossum, levkivskyi, pablogsal, serhiy.storchaka, yselivanov
Date 2018年05月11日.09:52:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526032339.65.0.682650639539.issue33346@psf.upfronthosting.co.za>
In-reply-to
Content
I think this can be fixed simpler. Currently a comprehension become asynchronous in two cases:
1. Explicitly, when it contains 'async for'. This is visible at AST level.
2. Implicitly, when any of inner expressions contains 'await'.
But asynchronous comprehensions should behave the same way as 'await'. I think that a comprehension should be made implicitly asynchronous if any of inner expressions contains explicit or implicit asynchronous comprehension. This is implemented in PR 6766.
History
Date User Action Args
2018年05月11日 09:52:19serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, ericvw, asvetlov, yselivanov, levkivskyi, pablogsal
2018年05月11日 09:52:19serhiy.storchakasetmessageid: <1526032339.65.0.682650639539.issue33346@psf.upfronthosting.co.za>
2018年05月11日 09:52:19serhiy.storchakalinkissue33346 messages
2018年05月11日 09:52:19serhiy.storchakacreate

AltStyle によって変換されたページ (->オリジナル) /