On Mon, Apr 11, 2011 at 03:16, Martin Sustrik <[email protected]> wrote:
> 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. > Yes, I did miss by a bit, thanks for the clarification. However, there's a pretty big difference between having one install dependency and two. Depending on the nature of this extra package, I imagine we might still end up deploying part of it inside pyzmq, rather than depending upon it. I fully appreciate the notion that devices are applications and applications don't belong in the core, so I certainly don't object to the move. I was just intending to point out the likely result of the change in the Python bindings. Thanks, -MinRK > > Martin >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
