➜

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.

classification
Title: input() call blocks multiprocessing
Type: behavior Stage:
Components: Windows Versions: Python 3.4, Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: paul.moore, steve.dower, the, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2016-04-29 09:54 by the, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg264480 - (view) Author: Stefan Forstenlechner (the) Date: 2016-04-29 09:54 
If input is called right away after applying a single job to multiprocessing.Pool or submitting concurrent.futures.ProcessPoolExecutor then the processes are not started. If multiple jobs are submitted everything works fine.

This only seems to be a problem on Windows (probably only 10) and python version 3.x

See my stackoverflow question: http://stackoverflow.com/questions/36919678/python-multiprocessing-pool-does-not-start-right-away
History
Date User Action Args
2022-04-11 14:58:30adminsetgithub: 71070
2016-04-29 09:54:24thecreate