Issue 26883: input() call blocks multiprocessing

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/71070

classification

Title:	input() call blocks multiprocessing
Type:	behavior	Stage:
Components:	Windows	Versions:	Python 3.4, Python 3.5

process

Dependencies:	Superseder:
Status:	open	Resolution:
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

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:30	admin	set	github: 71070
2016年04月29日 09:54:24	the	create

homepage