njsmith
commented
6 years ago So there's two ways to integration zmq with asyncio:
- Define a custom asyncio event loop that has special support for zmq, and then use this everywhere.
- Use zmq's annoying and error-prone notification API to get it working on top of a normal asyncio event loop.
pyzmq implements all the low-level bindings you need to do anything with zmq in Python, and then also provides an implementation of option (1).
aiozmq uses pyzmq's low-level bindings, but then implements option (2) on top of them.
In Trio, option (1) is not possible. So we have to do the equivalent of option (2), where we use pyzmq's low-level bindings and hook them up to Trio's built-in event loop. That's what the notes in the trzmq repository are about. (This is also why trzmq is not a totally trivial thing. I don't think it should be too hard, I believe the notes there do describe all the issues, but it took a while to figure that out, which is why I haven't actually finished it :-).)
goodboy
As has always been the plan (because it fits the actor model so well) we need native zeromq support. This will likely need a little thinking and re-design to integrate with the current
Channelapi.Some prerequisites before this can move forward:
triosupport; @njsmith has some notes intrzmqin order to make this work alongsidepyzmq.