[issue1395552] add support for thread function result storage

Michal Božoň added the comment: i still do not agree, it will always feel somehow incomplete, being able to easily "threadize" the function: >>> t = threading.Thread(target=func) and then not being able to get the target function result (easily) -- __

[issue1395552] add support for thread function result storage

R. David Murray 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

[issue1395552] add support for thread function result storage

Michal Božoň added the comment: why would we throw the thread function result out of the window? because there is a another way, to do it? there are always many ways, how to do it, so why would we want to do it very difficult way? i think that not having the result stored somewhere is a bug and

[issue1395552] add support for thread function result storage

Changes by Daniel Diniz : -- priority: normal -> low stage: -> patch review type: -> feature request versions: +Python 2.7, Python 3.1 -Python 2.4 ___ Python tracker ___