Author tomMoral
Recipients davin, grzgrzgrz3, pitrou, tomMoral, xiang.zhang
Date 2017-06-02.15:01:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496415707.66.0.968317966833.issue30414@psf.upfronthosting.co.za>
In-reply-to
Content
This fix, while preventing the Queue to crash, does not give any way to  programatically detect that the message was dropped. This is a problem as we can no longer assume that the Queue will not drop messages. For instance, we can no longer detect deadlocks in concurrent.futures.ProcessPoolExecutor as done in https://github.com/python/cpython/pull/1013 where the crashed QueueFeederThread was used to monitor the working state of the executor.

We could either:
- Put a flag highlighting the fact that some messages where dropped.
- Add an argument to the Queue to close on pickling errors.

I'd be happy to work on a PR to implement any solution that you think is reasonable.
History
Date User Action Args
2017-06-02 15:01:47tomMoralsetrecipients: + tomMoral, pitrou, davin, xiang.zhang, grzgrzgrz3
2017-06-02 15:01:47tomMoralsetmessageid: <1496415707.66.0.968317966833.issue30414@psf.upfronthosting.co.za>
2017-06-02 15:01:47tomMorallinkissue30414 messages
2017-06-02 15:01:47tomMoralcreate