Pinning pyzmq requirement to 2.2.0.1 #57
Conversation
Pinning pyzmq requirement to 2.2.0.1, instead of saying anything above 2.2.0.1 is good, because it is breaking due to pyzmq 13.0 We should pin to 2.2.0.1 until we know it works fine on a higher version.
|
I am concern that it might bother people who also use the latest version of ZMQ directly. Hopefully tonight (PST) I will either fix the problem with the latest version of pyzmq, or accept your patch, either way, I will update the package on pypi. |
|
Any update on this? If you don't have time to pull/merge and push to pypi, just let me know and I can do it. |
|
god dammit, totally lost track of time grrr. I am setting up a reminder to On Wed, Mar 6, 2013 at 2:17 PM, Ken Cochrane notifications@github.comwrote:
|
|
OK, thanks. |
|
See this commit: cf3741c I tested it with pyzmq 13.0.0 and the older pyzmq-static 2.1.11.2, it seems to work for me Please confirm that this is working for you with the latest master. I will then bump the version and update the package on pipy. Best, |
|
Seems to be working with the latest version of zmq and zerorpc 0,4,2. |
Pinning pyzmq requirement to 2.2.0.1, instead of saying anything above 2.2.0.1 is good, because it is breaking due to pyzmq 13.0
We should pin to 2.2.0.1 until we know it works fine on a higher version.