Open JensRantil opened 11 years ago
Playing devil's advocate but aren't those features of ∅MQ and not specific to PyZMQ? Do they warrant mentioning when speaking of a wrapper for that service?
Good call! I just read http://docs.python-guide.org/en/latest/notes/styleguide/#relevancy which states
Avoid including too much information on subjects that don’t directly relate to Python development.
I had not read the passage before. Instead I guess we should probably:
remove the list of "basic patterns" since it is not really relevant to Python
:+1:
Change the link
What about including both and giving the reader the option to choose which they wish to know more about? I had to do some ZMQ research recently and ended up using both as a reference. I still don't feel I know it (or its API) well enough to know which is more or less useful.
What about including both and giving the reader the option to choose which they wish to know more about? I had to do some ZMQ research recently and ended up using both as a reference. I still don't feel I know it (or its API) well enough to know which is more or less useful.
:+1: I'll see if I can make a pull request on this when I have the time.
:+1: You're awesome
Improvements to http://docs.python-guide.org/en/latest/scenarios/network/#pyzmq; Mention that it supports in-process message passing, inter-process message passing and tcp message passing.