[zeromq-dev] Removal of zmq_device[3] from 3.0

[Martin Sustrik]

Hi Min,

> zmq_device is particularly valuable in Python.  Due to Python's infamous
> GIL, having
> a C-thread that will remain responsive regardless of blocking Python
> code (e.g. a FORWARDER device as heartbeat)
> is a pretty big deal.
>
> I imagine that when we bring pyzmq up to speed on 3.0, we will have to
> reimplement some amount of zmq_device
> in Cython to restore this extremely useful functionality.

I think you misunderstood. The idea is to split devices into a separate 
project, not to ditch them.

Martin