A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2016-October/146772.html below:

[Python-Dev] Clarification for concurrent.futures.Future

[Python-Dev] Clarification for concurrent.futures.Future [Python-Dev] Clarification for concurrent.futures.FutureMark Spruiell mes at zeroc.com
Fri Oct 28 12:51:07 EDT 2016
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>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4