[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-11-11 Thread Richard Oudkerk
Richard Oudkerk added the comment: Fixed by #11161. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> futures.ProcessPoolExecutor hangs ___ Python tracker ___

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-10-25 Thread Brian Quinlan
Brian Quinlan added the comment: Take a look at http://bugs.python.org/issue11161 and its fix. Do you think that just saying that ProcessPoolExecutor will not work from the interactive shell is sufficient? -- nosy: +bquinlan ___ Python tracker

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-05-01 Thread Richard Oudkerk
Richard Oudkerk added the comment: > Ah. Then, a documentation error. The error message ("queue.Full"?) and > the documentation are totally not clear about that. Once something goes wrong you are likely to get a cascade of errors, and the first one reported is not necessarily the original caus

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-04-30 Thread Decade
Decade added the comment: Ah. Then, a documentation error. The error message ("queue.Full"?) and the documentation are totally not clear about that. Does ProcessPoolExecutor just not require tasks to be picklable in Unix? Also, this raises questions about what exactly "picklable" means, and wh

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-04-30 Thread Richard Oudkerk
Richard Oudkerk added the comment: Some sort of error is expected. On Windows any functions or classes used in a task sent the executor must be picklable/unpicklable. This means that they must be defined in an importable module rather than being defined in the interactive shell. On Unix, you

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-04-29 Thread Decade
Decade added the comment: Oh, yeah, using Python 3.3.1 (v3.3.1:d9893d13c628, Apr 6 2013, 20:30:21) [MSC v.1600 64 bit (AMD64)] on win32 -- ___ Python tracker ___ __

[issue17874] ProcessPoolExecutor in interactive shell doesn't work in Windows

2013-04-29 Thread Theodore Randolph
New submission from Theodore Randolph: ProcessPoolExecutor doesn't work in an interactive shell in Windows, such as IDLE or the command prompt. It does work in Unix, and it works if I use the ThreadPoolExecutor instead. For example, let's use the tutorial at http://eli.thegreenplace.net/2013/