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 tomMoral
Recipients tomMoral
Date 2017-10-05.07:41:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507189305.87.0.213398074469.issue31699@psf.upfronthosting.co.za>
In-reply-to
Content
When using `concurrent.futures.ProcessPoolExecutor` with objects that are not picklable or unpicklable, several situations results in a deadlock, with the interpreter freezed.

This is the case for different scenario, for instance these three : https://gist.github.com/tomMoral/cc27a938d669edcf0286c57516942369

The different pickling/unpickling error and their effect should be tested in `test_concurrent_futures.py`
History
Date User Action Args
2017-10-05 07:41:45tomMoralsetrecipients: + tomMoral
2017-10-05 07:41:45tomMoralsetmessageid: <1507189305.87.0.213398074469.issue31699@psf.upfronthosting.co.za>
2017-10-05 07:41:45tomMorallinkissue31699 messages
2017-10-05 07:41:45tomMoralcreate