Message 264480 - Python tracker

➜

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.

In-reply-to
Author	the
Recipients	paul.moore, steve.dower, the, tim.golden, zach.ware
Date	2016年04月29日.09:54:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1461923664.77.0.748212868392.issue26883@psf.upfronthosting.co.za>

Content
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

Content

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
2016年04月29日 09:54:24	the	set	recipients: + the, paul.moore, tim.golden, zach.ware, steve.dower
2016年04月29日 09:54:24	the	set	messageid: <1461923664.77.0.748212868392.issue26883@psf.upfronthosting.co.za>
2016年04月29日 09:54:24	the	link	issue26883 messages
2016年04月29日 09:54:24	the	create

homepage