[New-bugs-announce] [issue26883] input() call blocks multiprocessing

Stefan Forstenlechner report at bugs.python.org
Fri Apr 29 05:54:24 EDT 2016

New submission from Stefan Forstenlechner:

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

components: Windows
messages: 264480
nosy: Stefan Forstenlechner, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: input() call blocks multiprocessing
type: behavior
versions: Python 3.4, Python 3.5

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list