Message 270330 - 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.

Author	tim.peters
Recipients	JA, tim.peters
Date	2016-07-13.17:24:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1468430663.37.0.52218041358.issue27508@psf.upfronthosting.co.za>
In-reply-to

Content
Note: this started on stackoverflow: https://stackoverflow.com/questions/38356584/python-multiprocessing-threading-code-exits-early I may be missing something obvious, but the only explanation I could think of for the behavior seen on Ubuntu is that the threads in the worker processes are being treated as daemon threads. The program works as intended for me on Windows - but, of course, there's a universe of differences between spawning (Windows) and forking (Ubuntu) processes too.

Note:  this started on stackoverflow:

https://stackoverflow.com/questions/38356584/python-multiprocessing-threading-code-exits-early

I may be missing something obvious, but the only explanation I could think of for the behavior seen on Ubuntu is that the threads in the worker processes are being treated as daemon threads.  The program works as intended for me on Windows - but, of course, there's a universe of differences between spawning (Windows) and forking (Ubuntu) processes too.

History
Date	User	Action	Args
2016-07-13 17:24:23	tim.peters	set	recipients: + tim.peters, JA
2016-07-13 17:24:23	tim.peters	set	messageid: <1468430663.37.0.52218041358.issue27508@psf.upfronthosting.co.za>
2016-07-13 17:24:23	tim.peters	link	issue27508 messages
2016-07-13 17:24:23	tim.peters	create