This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gjwebber
Recipients docs@python, gjwebber, pitrou
Date 2013-04-09.13:59:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365515985.35.0.134296368755.issue17674@psf.upfronthosting.co.za>
In-reply-to
Content
Just ran the example code linked here again for my own sanity:
http://docs.python.org/dev/library/concurrent.futures.html#processpoolexecutor-example

Exactly the same thing happened. Here is the Traceback:
Traceback (most recent call last):
  File "<string>", line 420, in run_nodebug
  File "<module1>", line 28, in <module>
  File "<module1>", line 24, in main
  File "C:\Python33\lib\concurrent\futures\_base.py", line 546, in result_iterator
    yield future.result()
  File "C:\Python33\lib\concurrent\futures\_base.py", line 399, in result
    return self.__get_result()
  File "C:\Python33\lib\concurrent\futures\_base.py", line 351, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
History
Date User Action Args
2013-04-09 13:59:45gjwebbersetrecipients: + gjwebber, pitrou, docs@python
2013-04-09 13:59:45gjwebbersetmessageid: <1365515985.35.0.134296368755.issue17674@psf.upfronthosting.co.za>
2013-04-09 13:59:45gjwebberlinkissue17674 messages
2013-04-09 13:59:45gjwebbercreate