New submission from Xavier Morel <xavier.mo...@masklinn.net>:
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? ---------- components: Library (Lib) messages: 403181 nosy: xmorel priority: normal severity: normal status: open title: concurrent.futures.Future should be suitable for use outside of executors type: enhancement versions: Python 3.10 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue45365> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
