Message 298038 - 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	vstinner
Recipients	vstinner
Date	2017年07月10日.09:27:06
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1499678826.37.0.565527833699.issue30886@psf.upfronthosting.co.za>

Content
https://github.com/python/cpython/pull/2642 fixes the warning. I tested the change with test_handle_called_with_mp_queue-bug.patch: no more warning. Sorry, I don't know multiprocessing to understand the purpose of the removed test. I would like to really make sure that a Queue object doesn't "leak" a thread when I close .close() + .join_thread(). It's surprising that .join_thread() doesn't join anything and leave a thread running in the background. Even if in the common case, when the system load is low, the thread quits quickly thanks to .close().

Content

https://github.com/python/cpython/pull/2642 fixes the warning. I tested the change with test_handle_called_with_mp_queue-bug.patch: no more warning.
Sorry, I don't know multiprocessing to understand the purpose of the removed test.
I would like to really make sure that a Queue object doesn't "leak" a thread when I close .close() + .join_thread(). It's surprising that .join_thread() doesn't join anything and leave a thread running in the background. Even if in the common case, when the system load is low, the thread quits quickly thanks to .close().

History
Date	User	Action	Args
2017年07月10日 09:27:06	vstinner	set	recipients: + vstinner
2017年07月10日 09:27:06	vstinner	set	messageid: <1499678826.37.0.565527833699.issue30886@psf.upfronthosting.co.za>
2017年07月10日 09:27:06	vstinner	link	issue30886 messages
2017年07月10日 09:27:06	vstinner	create

homepage