Eric Meyer added the comment:
The problem I was seeing ended up being improper GIL management in a c++
extension. It seems putting items that were created without the GIL on the
queue causes a seg fault.
--
___
Python tracker
<ht
Eric Meyer added the comment:
multiprocessing.SimpleQueue is another workaround to this issue.
I agree the docs should be clearer about this. Additionally, it would be
helpful if there was a way to optionally put an item on a multiprocessing.Queue
and block until the item has been written
