➜
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.
Created on 2017-06-20 04:34 by Damien George, last changed 2022-04-11 14:58 by admin.
| Messages (2) | |||
|---|---|---|---|
| msg296400 - (view) | Author: Damien George (Damien George) | Date: 2017-06-20 04:36 | |
The behaviour of the "async with" statement in CPython does not match the description of it in PEP492, nor the language documentation. The implementation uses a try/except/finally block, while the PEP and documentation describe the behaviour using a try/except/else block. The PEP and documentation should be updated to reflect the true intention of "async with". |
|||
| msg296402 - (view) | Author: Nick Coghlan (ncoghlan) *  |
Date: 2017-06-20 05:38 | |
The specific issue is that early exits from an "async with" statement are actually defined the same way they for synchronous with statements: exiting early via return, break, or continue, is the same as reaching the end of the try block. However, that's not what the documentation currently says: it describes "async with" in terms of try/except/else, which isn't correct. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:47 | admin | set | github: 74892 |
| 2017-06-20 05:38:31 | ncoghlan | set | nosy:
+ ncoghlan, yselivanov messages: + msg296402 |
| 2017-06-20 04:36:45 | Damien George | set | messages: + msg296400 |
| 2017-06-20 04:34:20 | Damien George | create | |