[zeromq-dev] pyzmq version when built against libzmq master (head)

Brian Knox briank at talksum.com
Sun Mar 11 23:14:58 CET 2012


Ok, good deal.  Thanks for the information!

Brian

On Sun, Mar 11, 2012 at 5:57 PM, MinRK <benjaminrk at gmail.com> wrote:

> On Sun, Mar 11, 2012 at 14:38, Brian Knox <briank at talksum.com> wrote:
> > Will the pyzmq version number track the zmq version going forward, when
> > zmq 3.1 is final?  Or is the fact that pyzmq and zmq are both on 2.1.x
> > coincidental?
>
> pyzmq follows libzmq releases because we have bdists that include
> libzmq itself, so the first pyzmq release after libzmq-3.1 is *stable*
> will match.
>
>
> >
> > Brian
> >
> > On 3/11/2012 5:09 PM, MinRK wrote:
> >> The version of pyzmq *itself* doesn't change when you build against
> >> different versions of libzmq.
> >>
> >> If you want to check against libzmq version, use: `zmq.zmq_version()`,
> >> which calls the zmq_version function in the underlying C library.
> >>
> >> -MinRK
> >>
> >>
> >> On Sun, Mar 11, 2012 at 13:38, Brian Knox<briank at talksum.com>  wrote:
> >>> I'm working on testing some code against pyzmq zeromq 3.1
> (specifically, the
> >>> head of libzmq as of a couple of days ago).  I'm running into a problem
> >>> where pyzmq built as an rpm (via python ./setup.py bdist_rpm) reports
> it's
> >>> version as 2.1dev.  If I run python ./setup.py build, I see the proper
> >>> version number detected:
> >>>
> >>> --------------------------
> >>> Configure: Autodetecting ZMQ settings...
> >>>      Custom ZMQ dir:       /usr/local
> >>> gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
> >>> -Wstrict-prototypes -fPIC -I/usr/local/include -Izmq/utils -Izmq/core
> >>> -Izmq/devices -c detect/vers.c -o detect/vers.o
> >>> gcc -pthread detect/vers.o -L/usr/local/lib -Wl,-R/usr/local/lib -lzmq
> -o
> >>> detect/vers
> >>>      ZMQ version detected: 3.1.1
> >>> ******************************************
> >>> ******************************************
> >>> Warning: Detected ZMQ version: 3.1.1. pyzmq's support for libzmq-dev is
> >>> experimental.
> >>> ******************************************
> >>> ---------------------
> >>>
> >>> But looking in the generated spec:
> >>>
> >>> %define name pyzmq
> >>> %define version 2.1dev
> >>> %define unmangled_version 2.1dev
> >>> %define release 1
> >>>
> >>> This is causing an issue when trying to test salt against the 3.1 dev
> >>> branch.  The code in pyzmq around detecting / setting the zmq version
> is
> >>> quite complex, so I figured I'd ask for pointers on how to hack the
> version
> >>> return.
> >>>
> >>> Thanks!
> >>> Brian
> >>>
> >>> _______________________________________________
> >>> zeromq-dev mailing list
> >>> zeromq-dev at lists.zeromq.org
> >>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >>>
> >> _______________________________________________
> >> zeromq-dev mailing list
> >> zeromq-dev at lists.zeromq.org
> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120311/ccee1b10/attachment.htm>


More information about the zeromq-dev mailing list