➜

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.

classification
Title: Make concurrent.futures.Future usable outside of executors
Type: enhancement Stage: test needed
Components: Library (Lib) Versions: Python 3.11
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: xmorel
Priority: normal Keywords:

Created on 2021-10-04 19:31 by xmorel, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg403181 - (view) Author: Xavier Morel (xmorel) * Date: 2021-10-04 19:31 
concurrent.futures.Future currently has the note:

> Future instances are created by Executor.submit() and should not be created directly except for testing.

That seems like a shame as futures are useful concurrency construct and having to rebuild them "by hand" seems like a waste.

What are the issues which prevent safely using futures outside of executors, and is there a way they could be fixed / lifted?
History
Date User Action Args
2022-04-11 14:59:50adminsetgithub: 89528
2021-10-08 21:22:50terry.reedysettitle: concurrent.futures.Future should be suitable for use outside of executors -> Make concurrent.futures.Future usable outside of executors
stage: test needed
versions: + Python 3.11, - Python 3.10
2021-10-04 19:31:22xmorelcreate