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 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>
In-reply-to
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:06vstinnersetrecipients: + vstinner
2017-07-10 09:27:06vstinnersetmessageid: <1499678826.37.0.565527833699.issue30886@psf.upfronthosting.co.za>
2017-07-10 09:27:06vstinnerlinkissue30886 messages
2017-07-10 09:27:06vstinnercreate