Message 316390 - Python tracker
Message316390
| 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:19 | serhiy.storchaka | set | recipients: + serhiy.storchaka, gvanrossum, ericvw, asvetlov, yselivanov, levkivskyi, pablogsal |
| 2018-05-11 09:52:19 | serhiy.storchaka | set | messageid: <1526032339.65.0.682650639539.issue33346@psf.upfronthosting.co.za> |
| 2018-05-11 09:52:19 | serhiy.storchaka | link | issue33346 messages |
| 2018-05-11 09:52:19 | serhiy.storchaka | create | |