[issue36120] Regression - Concurrent Futures

Cheryl Sabella added the comment: Thank you. I just tried running the example and it worked OK for me in the 3.8 master build. I believe your report is a duplicate of issue 35797. -- resolution: -> duplicate stage: test needed -> resolved status: open -> closed superseder: -> conc

[issue36120] Regression - Concurrent Futures

Jonathan added the comment: The "ProcessPoolExecutor Example" on this page breaks for me: https://docs.python.org/3/library/concurrent.futures.html -- ___ Python tracker ___

[issue36120] Regression - Concurrent Futures

Cheryl Sabella added the comment: Thank you for the report. Please add a script that contains the least amount of code that would replicate the error. Thanks! >From the devguide: > last but not least, you have to describe the problem in detail, including > what you expected to happen, what

[issue36120] Regression - Concurrent Futures

Jonathan added the comment: There's also this error too: Traceback (most recent call last): File "c:\_libs\Python37\lib\multiprocessing\process.py", line 297, in _bootstrap self.run() File "c:\_libs\Python37\lib\multiprocessing\process.py", line 99, in run self._target(*self._args

[issue36120] Regression - Concurrent Futures

New submission from Jonathan : I'm using Concurrent Futures to run some work in parallel (futures.ProcessPoolExecutor) on windows 7 x64. The code works fine in 3.6.3, and 3.5.x before that. I've just upgraded to 3.7.2 and it's giving me these errors: Process SpawnProcess-6: Traceback (most re