Message 354823 - 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	vstinner
Recipients	jkloth, miss-islington, vstinner
Date	2019-10-16.23:43:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1571269423.53.0.781670380824.issue38207@roundup.psfhosted.org>
In-reply-to

Content
On Windows, the threads reading pipes continue to run even after the direct child process exited. Problem: at Python exit (main process), Python hangs on calling threading._shutdown() which waits until all Python threads complete. One enhancement would be to spawn subprocess.Popen.communicate() internal threads as daemon threads. So threading._shutdown() would not wait for them at Python exit.

On Windows, the threads reading pipes continue to run even after the direct child process exited.

Problem: at Python exit (main process), Python hangs on calling threading._shutdown() which waits until all Python threads complete.

One enhancement would be to spawn subprocess.Popen.communicate() internal threads as daemon threads. So threading._shutdown() would not wait for them at Python exit.

History
Date	User	Action	Args
2019-10-16 23:43:43	vstinner	set	recipients: + vstinner, jkloth, miss-islington
2019-10-16 23:43:43	vstinner	set	messageid: <1571269423.53.0.781670380824.issue38207@roundup.psfhosted.org>
2019-10-16 23:43:43	vstinner	link	issue38207 messages
2019-10-16 23:43:43	vstinner	create