Issue 32364: Add AbstractFuture and AbstractTask (original) (raw)
Issue32364
➜
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.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/76545
classification
| Title: | Add AbstractFuture and AbstractTask | ||
|---|---|---|---|
| Type: | Stage: | ||
| Components: | asyncio, Library (Lib) | Versions: | Python 3.8 |
process
| Status: | open | Resolution: | |
|---|---|---|---|
| Dependencies: | Superseder: | ||
| Assigned To: | Nosy List: | asvetlov, yselivanov | |
| Priority: | normal | Keywords: |
Created on 2017-12-18 11:13 by asvetlov, last changed 2022-04-11 14:58 by admin.
| Messages (3) | ||
|---|---|---|
| msg308543 - (view) | Author: Andrew Svetlov (asvetlov) *  |
Date: 2017-12-18 11:13 |
| Asyncio supports custom future and task by third-party loop implementation. Abstract classes for them is needed. AbstractTask should not have set_result()/set_exception() maybe, is this case abstract base is needed (AbstractPromise, AbstractCancellableValue or whatever). | ||
| msg308578 - (view) | Author: Yury Selivanov (yselivanov) * |
Date: 2017-12-18 18:05 |
| +1, let's do it. I'd add a new module - 'asyncio.abc' and put them both there (as well as asyncio.isfuture() function). | ||
| msg308771 - (view) | Author: Andrew Svetlov (asvetlov) * |
Date: 2017-12-20 18:49 |
| Let's postpone it to Python 3.8 |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:55 | admin | set | github: 76545 |
| 2017-12-20 18:49:03 | asvetlov | set | messages: + versions: + Python 3.8, - Python 3.7 |
| 2017-12-18 18:05:24 | yselivanov | set | messages: + |
| 2017-12-18 11:13:10 | asvetlov | create |