[zeromq-dev] PyZMQ support for socket options added in ZeroMQ 2.1

MinRK benjaminrk at gmail.com
Thu Nov 11 01:26:06 CET 2010


Hello,

On Wed, Nov 10, 2010 at 15:50, Martin Lucina <mato at kotelna.sk> wrote:

> Hi,
>
> I need to add support for some of the new socket options added in ZeroMQ
> 2.1 to PyZMQ for an application I'm developing, however I'm having problems
> figuring out what version of Cython to use. On my Debian lenny system, if I
> use the distro-provided version (0.9.8) I get:
>
> cythoning zmq/_zmq.pyx to zmq/_zmq.c
>
> Error converting Pyrex file to C:
> ------------------------------------------------------------
> ...
> cdef extern from "Python.h":
>    object PyCObject_FromVoidPtr(void *, void (*)(void*))
>
> #---------------------------------------------------------------------
>
> cdef inline void *memnew(size_t n):
>                               ^
> ------------------------------------------------------------
>
> /home/mato/src/pyzmq/zmq/allocate.pxi:9:32: Expected ')'
>

I really recommend using current github master over 2.0.8, until we cut a
2.0.10 release, at least.  Note that pyzmq master remains 2.0.x targeted,
since we haven't moved up to 2.1.x yet, and we will definitely cut a 2.0.x
release before that happens in master.


>
> I've tried building 0.12.1 from the Debian source package, but that
> produces even more errors.
>

I'm not 100% sure, but we *may* depend on current Cython (13), which is
easy_install-able as of August.


>
> Any hints? Or, pretty please, could one of you PyZMQ people add support for
> ZMQ_LINGER to the 2.0.x branch? With the new ZMQ_VERSION constants that
> should be possible to do in a way that would be backward-compatible.
>
> The reason I wanted to start with PyZMQ 2.0.x is that all my code is
> developed on PyZMQ 2.0.x (but ZeroMQ master) and I'd rather not transition
> to PyZMQ master just now.
>

PyZMQ master is quite stable, and still targets 2.0.x, but we haven't cut a
release since 2.0.8, mostly for lack of time.  We don't do development in
master, we do it all in feature branches, then merge into master when the
feature is complete.  The difference between current master and a 2.0.10
release would be very very small, if anything at all.  I'm not sure that
there is any 2.0.8 code that would not work on master, so I would be
surprised if updating causes a problem.  Please let us know if it does.

I'll try to cut 2.0.10, or at least 2.0.10rc soon, if you would prefer that.

In any case, adding ZMQ_LINGER support should be as simple as adding two
lines in zmq/core/constants.pyx

-MinRK


>
> Thanks in advance,
>
> -mato
> _______________________________________________
> 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/20101110/f9569da3/attachment.htm>


More information about the zeromq-dev mailing list