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 <rep...@bugs.python.org> <http://bugs.python.org/issue26883> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
