Running on Windows XP 32-bit.
Uninstalled Python 2.7, installed Python 3.3.

I asked a question on stack overflow, detailing the problem and supplying example code and Traceback here:
http://stackoverflow.com/questions/15900366/all-example-concurrent-futures-code-is-failing-with-brokenprocesspool

More info on request if required.

Forgot to mention, the posted code works for another SO user on Debian and OS X.

This is not the example code. The example code uses a main() function which is guarded by a "if" block:

if __name__ == '__main__':
    main()

See http://docs.python.org/2/library/multiprocessing.html#windows for explanations.

Also, perhaps the concurrent.futures docs could point to that paragraph.

As mentioned in the previously linked post, I copy-pasted the example code shown here:
http://docs.python.org/dev/library/concurrent.futures.html#processpoolexecutor-example

Which resulted in exactly the same error as the 'more simple' example I provided.

There is no mention of anything Windows specific on the documentation page, or any hints as to why this may not be working.

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.

Ok, can someone else confirm the issue on Windows?

The example code works for me on 3.3.0 on Windows 8. I'd have to find a VM to try out XP like gjwebber - will look later.

@gjwebber: How exactly are you running the program to get that traceback?

The following lines make it look like you are doing something non-standard (as opposed to just saving the file and running it from the command line):

  File "<string>", line 420, in run_nodebug
  File "<module1>", line 28, in <module>
  File "<module1>", line 24, in main

Damn, this was my screw up. It was a combination of two things that threw me off:

1. I was running my (saved) code un-gaurded, but was getting the same error as with the example code. I thought the problem was elsewhere.

2. As it was just example code, I was copy-pasting it into my IDE and running it. This caused the slightly weird looking Traceback that Richard Oudkerk pointed out and the same error message.

After saving and running the standard example, everything worked as expected. After this, I added the 'main' guard to my code and that fixed the problem there.

Sorry about that, looks like there's no problem after all. Tested at home on Win 7 and on my works machine (XP Pro).

Regards,
Gareth