[issue1395552] add support for thread function result storage

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

I agree with Stephen.  You can implement this functionality easily
through the current API (subclassing), so there's no need to complicate
the existing API to handle this one communication method as a special case.

Furthermore, this particular use case is the tip of a small iceberg
usually called "Futures", which provides a much cleaner API for the use
case.  There has been a suggestion to include such a package in core,
though it will probably be some time before the library is mature enough
for a decision to be made.

----------
nosy: +r.david.murray
resolution:  -> rejected
stage: patch review -> committed/rejected
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1395552>
_______________________________________