[Python-Dev] Clarification for concurrent.futures.Future (original) (raw)
Mark Spruiell mes at zeroc.com
Fri Oct 28 12:51:07 EDT 2016
- Previous message (by thread): [Python-Dev] Default formatting
- Next message (by thread): [Python-Dev] Clarification for concurrent.futures.Future
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The docs for this class state:
"Future instances are created by Executor.submit() and should not be created directly except for testing."
https://docs.python.org/3/library/concurrent.futures.html#future-objects
We have a need for a thread-safe future type in our extension but this statement makes us hesitate to use it. We don't need the executor functionality.
We can write our own future class easily enough, we're just wondering what the justification was for the limitations mentioned in the docs.
Thanks,
Mark Spruiell ZeroC, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20161028/0f31a137/attachment.html>
- Previous message (by thread): [Python-Dev] Default formatting
- Next message (by thread): [Python-Dev] Clarification for concurrent.futures.Future
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]