On Thu, Jul 28, 2016 at 2:28 PM, Frédéric wrote:
> Le jeudi 28 juillet 2016, MinRK a écrit :
>
> > Following the behavior of Python 3.5, interrupted system calls are
> > retried, starting in pyzmq 14.7.
>
> I tried added a manual retry, but this does not help.
>
>
Following the behavior of Python 3.5, interrupted system calls are retried,
starting in pyzmq 14.7. Are you creating the sockets after forking with
multiprocessing? You shouldn't use any sockets that were created in the
host process in any of the forks.
-MinRK
On Thu, Jul 28, 2016 at 1:
On Wed, Mar 16, 2016 at 11:06 AM, Pieter Hintjens wrote:
> Off-topic, but I need to ask, how do you do the syntax highlighting in
> emails?
>
http://markdown-here.com/
>
> On Mon, Mar 14, 2016 at 4:42 PM, MinRK wrote:
> > On Sat, Mar 12, 2016 at 9:00 PM, Da
code than
thread-safe code, since all context switching is explicit (make sure you
have no yield calls in the middle of an operation).
-MinRK
> Any enlightenment will be welcome.
>
> And, by the way, I suspect that something equivalent could be done
> in Node.js (JavaScript), which also
Typically, with bind you want an IP address. Often a domain works, but it
requires that zeromq can resolve that domain to a *local* IP address of the
machine. This won’t work, for instance, if your raspberry pi is behind a
router. You can listen on all IPs by using 'tcp://*:10011'.
-Min
I think tweetnacl by default makes sense.
On Wed, Feb 10, 2016 at 11:40 PM, Pieter Hintjens wrote:
> Hi all,
>
> I'd like to start moving to tweetnacl as the default when building
> libzmq. This means, no separate install of libsodium, and encryption
> built in by default. We can still have a --
ing the other FDs to get signaled.
>
> The bottom line, this is kind of syntactic sugar, it will be the
> equivalent of calling has_in or has_out immediately after FD is signaled
> and only then call recv/send.
>
Gotcha, thanks for the explanation. I think this will still be a huge
impr
readable? If they both have to be read-only FDs, that seems fine,
as long as the signaling for send and recv are separated somehow. I'm not
sure what users would do with the Command FD.
-MinRK
> For thread safe sockets this is a little simpler as we can make one FD for
> all sockets for
ere a technical reason why we can't add a zmq.LEVEL_FD that would
behave in a more conventional manner:
- level-triggered
- signal write when socket is writable
- signal read when socket is readable
I would work on this myself, but unfortunately I don't think I have the
relevant exp
Am I right in understanding that this means that zeromq-4.1.5 won't support
an OS version that zeromq-4.1.2 supports? Does that seem like a problem to
anyone else?
Seems like the `if_nametoindex` patch should be reverted on the 4.1 series.
-MinRK
On Wed, Jan 13, 2016 at 12:15 PM, S
Windows, I believe there's an appveyor CI running.
> Though probably not testing the tweetnacl integration.
>
>
> On Mon, Jan 18, 2016 at 11:10 AM, MinRK wrote:
> > I added it to Makefile.am upstream, and opened a PR backporting that and
> the
> > Windows support to
ess appears to be undocumented.
-MinRK
On Mon, Jan 18, 2016 at 11:03 AM, Pieter Hintjens wrote:
> Not packaging tweetnacl was an oversight; someone added it to the
> project and did not update Makefile.am. I will make this change. I
> think it should also go into src/foreign rather than
I noticed that tweetnacl isn't included in the releases. Is this
intentional?
How are the tarballs made? I started trying to fix this, but didn't find
any documentation for how zeromq is released, and `make dist` seems to fail
due to missing Makefile sources in `build/cmake`.
-MinRK
O
https://github.com/zeromq/pyzmq/pull/745 should add GSSAPI to pyzmq, if you
want to give it a test.
On Thu, Nov 5, 2015 at 3:55 PM, Tevesz Ágnes wrote:
> Hi,
>
> I would like to ask that do you plan to expose the Kerberos security
> mechanism in PyZMQ too? I know the feature is available with cz
nd tornado
<http://pyzmq.readthedocs.org/en/latest/api/zmq.eventloop.future.html>.
https://pyzmq.readthedocs.org/en/latest/changelog.html
Wheels are building now, and should finish uploading before too long.
-MinRK
___
zeromq-dev mailing list
zeromq-dev
On Thu, Jul 2, 2015 at 10:55 AM, Christoph Buelter
wrote:
> Hey MinRK, thanks for answering.
>
> I don't do this on a regular basis, but for I example I just tried it with
> dulwich
> <https://github.com/jelmer/dulwich>and that worked fine.
>
> Basically wha
Can you build other Python extensions? Is PyZMQ the only one that fails?
On Wed, Jul 1, 2015 at 2:51 PM, Christoph Buelter
wrote:
> Hi,
>
> has anyone yet managed to build Windows with VC11 and Python 2.7.3?
> I am having all kinds of problems. The default Python 2.7.3 has been
> compiled with V
u need. I think you may
need a very recent Python 2.7 (.9 or .10, perhaps) for distutils to find
it, though.
-MinRK
On Tue, Jun 23, 2015 at 2:37 PM, Christoph Buelter
wrote:
> Hello,
>
> I am trying to build pyzmq on *Windows*, Python 2.7.3 x64 with Visual
> Studio 2012.
>
>
are unique as long as the objects exist, you should have
no collisions putting different objects in the dictionary from different
threads. You could also key by UUID if for some reason you have multiple
threads sending the same exact object.
-MinRK
>
> Rg,
>
> Arnaud
>
> On J
ast approach doesn’t hold a reference to the object while it’s
in transit, so it’s possible for the restoration to fail if the object has
been garbage collected in between send/recv.
-MinRK
On Thu, Jun 4, 2015 at 1:59 AM, Arnaud Loonstra wrote:
> On 2015-06-03 17:25, Arnaud Loonstra wrote:
ple shows getting the zyre socket as a PyZMQ socket
>
> >>> from zyre import Zyre
> >>> import zmq
> >>> z1 = Zyre('t1')
> >>> s = z1.socket()
> >>> print(s)
>
> >>> print(s.contents.endpoint)
> inpro
delocate-wheel wheelhouse/pyzmq-*.whl
```
and you should be set.
-MinRK
On Thu, Apr 16, 2015 at 1:44 PM, Thomas Maslach wrote:
> Thanks for the quick response..
>
>
>
> Regarding bdist, you said: Does it work if you specify an absolute path? I
> haven’t spent any time worki
disk (and not necessarily on my machine). I believe I
> can manually go to all the *.so files and call install_name_tool to
> redirect to my libzmq. But, that doesn’t seem like a clean solution.
>
There’s a great tool called delocate <https://pypi.python.org/pypi/delocate>
that auto
(pyzmq maintainer here)
I disagree with the sentiment expressed in the Guide. Either it belongs as
the libzmq default behavior itself, or it doesn't. It doesn't make sense to
me for language bindings to unanimously disagree with libzmq instead of
changing the underlying libzmq behavio
If you want to configure zeromq, you probably shouldn’t be using
--zmq=bundled. I would configure and install libzmq with --prefix=PREFIX,
then load it for pyzmq with setup.py install --zmq=PREFIX.
-MinRK
On Wed, Mar 11, 2015 at 11:37 AM, Michel Pelletier <
pelletier.mic...@gmail.com>
How did you install pyzmq? What OS is this?
-MinRK
On Wed, Mar 11, 2015 at 7:03 AM, Adam Najman wrote:
> I'm trying to establish a NORM connection using ZeroMQ as detailed here:
>
> http://zeromq.org/topics:norm-protocol-transport
>
> I've already built NORM and Zer
the examples repo
<https://github.com/imatix/zguide/blob/master/examples/Python/hwserver.py>
in the meantime.
-MinRK
On Sat, Mar 7, 2015 at 8:47 PM, Michael Cuggy wrote:
> Hello,
>
> "On your example, are you running the requisite request receiver, eg
> the python sc
Can you provide the complete output of installing pyzmq? And what happens
when you do `python -c import zmq`?
-MinRK
On Sat, Mar 7, 2015 at 3:28 PM, Michael Cuggy wrote:
> I am trying to run the Hello World python program taken from this link:
>
> http://zguide.zeromq.org/py:hwcli
On Sun, Feb 8, 2015 at 1:14 AM, Pieter Hintjens wrote:
> On Sun, Feb 8, 2015 at 12:53 AM, MinRK wrote:
>
> > I guess the problems I identified that it solves weren't really problems,
> > then.
>
> Where in the email below are you identifying the problems tha
On Sat, Feb 7, 2015 at 12:02 AM, Pieter Hintjens wrote:
> On Fri, Feb 6, 2015 at 9:28 PM, MinRK wrote:
>
> > There may be reasons this would be super gross and horrible, but it's an
> > idea, anyway.
>
> It didn't solve any identifiable problem, and forced ever
ls to zmq_send(..., SNDMORE), making it no better or worse than
making those several calls yourself.
-MinRK
>
> On Fri, Feb 6, 2015 at 2:40 PM, Michel Pelletier <
> pelletier.mic...@gmail.com> wrote:
>
>> Something else that occurred to me today, perhaps incorrectly, is that
>>
;s an
idea, anyway.
-MinRK
On Fri, Feb 6, 2015 at 9:02 AM, Thomas Rodgers
wrote:
> Adding a mutex, even one that is never contended, to the socket will
>> essentially triple this (one atomic CAS to acquire the mutex, one atomic
>> CAS to put the message on the pipe, one atomi
r more than 2-3, not generic comlicated hops), but I
had the same code working when zeromq-3.0 split routing information from
content (I think they were called 'command frames' or something?). I think
the main difference between this and the earlier attempt was the earlier
attempt used the
be a
bit more brief, and link to the tornado docs
<http://tornado.readthedocs.org/en/latest/ioloop.html#tornado.ioloop.IOLoop.add_callback>
.
-MinRK
> --
>
> From cf9418dc14b2dc2e1aca5be1b79a105982dcd877 Mon Sep 17 00:00:00 2001
> From: drebs
> Date: Tue, 3 Feb 2015 12:50:59 -0200
>
ove, it
seems that there's no plan for multipart to ever be removed. Deprecated
even seems like too strong a word for a useful feature that will continue
to be supported indefinitely. Or is anyone proposing the eventual removal
of multipart?
-MinRK
On Tue, Feb 3, 2015 at 9:37 AM, Arnaud Kapp
.
You want your ZmqREQConnection.send to hand off the stream.send to the
IOLoop’s thread via IOLoop.add_callback:
def send(self, *args, **kwargs):
print("Sending message to backend: (%s, %s)" % (args, kwargs))
self._ioloop.add_callback(lambda : self._stream.send(*args, **kwargs))
The inproc://zeromq.zap.01 url is hardcoded in libzmq
<https://github.com/zeromq/zeromq4-x/blob/v4.0.5/src/session_base.cpp#L285>.
The session internally creates a client connection to that endpoint.
-MinRK
On Fri, Dec 12, 2014 at 12:56 PM, Riskybiz wrote:
>
> I’m trying to impl
PyZMQ builds libzmq (and libsodium) as Python extensions, using the
compiler associated with Python (hence the need for VC9, the compiler
associated with Python.org 2.7). They are built with `setup.py build_ext`.
-MinRK
On Sat, Oct 11, 2014 at 1:15 PM, André Caron
wrote:
> Hi again!
>
&g
o message to receive. That's what NOBLOCK means – it will always
finish immediately, either returning a message if there is one, or raising
ZMQError(EAGAIN) if there is not.
-MinRK
>
> Regards,
> Karthik.
>
> __
It's not bundled simply because I couldn't build it on Windows. If you can
come up with a simple fix for building bundled libsodium, then I would
bundle libsodium on Windows.
-MinRK
On Thu, Oct 9, 2014 at 1:48 PM, André Caron wrote:
> Hi there!
>
> I'm try
in the
device received the message
2. it supports ROUTER-ROUTER devices, which can be used as multiplexers
If you aren't interested in either one of those, then the plain proxy that
ships with libzmq is probably what you are after.
-MinRK
&g
Can you run any/all of the scripts in examples/security?
What do you get from `zmq.curve_keypair()`?
On Tue, Jul 29, 2014 at 6:52 AM, Greg Ward wrote:
> Hey folks --
>
> I'm trying to build pyzmq 14.3.1, but getting a couple of test
> failures. One is intermittent, but the other seems to happe
there are
messages to be sent.
-MinRK
On Thu, Jul 3, 2014 at 7:07 AM, KIU Shueng Chuan wrote:
> How about replacing the Queue with zmq sockets? Then you could just add
> the "consumer" socket to the event loop.
> On 3 Jul 2014 16:15, "Indradhanush Gupta"
>
On Sun, Jun 15, 2014 at 11:55 AM, Indradhanush Gupta <
indradhanush.gu...@gmail.com> wrote:
>
>
>
> On Mon, Jun 16, 2014 at 12:17 AM, MinRK wrote:
>
>> To add further confusion, PyZMQ distinguishes term from destroy (pyzmq
>> used the term ‘destroy’ before zmq di
.
-MinRK
On Sun, Jun 15, 2014 at 6:03 AM, Pieter Hintjens wrote:
> zmq_term/zmq_init are an older deprecated API. We switched to a more
> consistent model for the API in 3.2, so zmq_ctx_xxx for all methods
> that work with contexts, like zmq_msg_xxx for all methods that work on
&
do:
https://pypi.python.org/pypi?%3Aaction=search&term=zeromq+rpc&submit=search
-MinRK
>
>
> -Michel
>
>
> On Mon, Apr 28, 2014 at 9:15 AM, Jess Updegrove wrote:
>
>> Hello Community!
>>
>> I'm a new programmer and I'm trying to build a serv
I just released pyzmq 14.2, which fixes a memory leak introduced in 14.0
when using `copy=False`.
https://pypi.python.org/pypi/pyzmq/14.2.0
-MinRK
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq
afe, so should only ever be used in
single-threaded applications, or with extreme caution. It's easy to
segfault with this if you are using sockets in threads.
-MinRK
> Using a mutex for socket close would have a penalty if many sockets need
> to be opened and closed quickly,
ombination.
> And do we have a published list of differences/features supported by the
> two backends?
>
The only known difference is a lack of support for zero-copy support in the
CFFI backend. Anything else is probably a bug.
-MinRK
>
> Lot's of questions. :) Thanks
That is indeed an interesting failure. How did you install libzmq and
libsodium? What is the output of a simple:
python -c 'import zmq; print(zmq.curve_keypair())'
-MinRK
On Fri, Mar 28, 2014 at 2:23 AM, Jonas Thiem wrote:
> -BEGIN PGP SIGNED MESSAGE-
> H
eerable function. I have used zmq_proxy daily
(since it was called zmq_device), with no issue. I don't actually have any
plan to expose the steerable version in pyzmq, because it doesn't offer any
real benefit in that context.
I don't think the steerable version of the function bel
I think backporting the function is okay, but that would mean that
zeromq4-x should become 4.1.x, and libzmq should be bumped to 4.2.
On Mon, Mar 17, 2014 at 1:04 AM, Pieter Hintjens wrote:
> We don't usually backport new functionality to existing stable
> releases, because it's been troublesom
I just released pyzmq-14.1.0, which adds implementations of authenticators
in zmq.auth, and bundled libsodium in bdists, so people are more likely to
have pyzmq with security available.
https://github.com/zeromq/pyzmq/releases/tag/v14.1.0
I will build the Windows bdists tomorrow.
-MinRK
age (once I release it), it would be:
pip install pyzmq>=14.1.0 --install-option="--zmq=bundled"
-MinRK
>
> Drew
>
> ___
> zeromq-dev mailing list
> zeromq-dev@lists.zeromq.org
> http://lists.zeromq.org/mailman/li
The weird errno should be fixed in
master<https://github.com/zeromq/pyzmq/pull/483>.
But this should only affect the case when libzmq is not linked against
libsodium. Are you sure that it is?
What is the output of ldd /path/to/libzmq.so?
-MinRK
On Tue, Feb 25, 2014 at 2:09 PM, Greg Ward
How did you build libzmq and/or install pyzmq? It could be that you don't
have libsodium linked, in which case the curve_keypair would fail. If
that's the case, obviously the error message should be better.
-MinRK
On Mon, Feb 24, 2014 at 3:47 PM, Greg Ward wrote:
> Hey all --
&g
On Tue, Feb 4, 2014 at 2:10 AM, Goswin von Brederlow
wrote:
On Mon, Feb 03, 2014 at 11:06:32AM -0800, MinRK wrote:
> > On Mon, Feb 3, 2014 at 10:57 AM, Michel Pelletier <
> > pelletier.mic...@gmail.com> wrote:
> >
> > > On Mon, Feb 3, 2014 at 9:30 AM, Greg
g it would be easier than trying to get the libraries compatible
> in-process. Then everybody wins, the libraries can cross-talk (via zmq)
> and you get the features you want in one library.
>
pyzmq does support auth in zmq.auth, b
existed
> because nothing was missing in pyzmq.
>
> But with zeromq 4.0 and CURVE there are parts that pyzmq lacks.
> Notably the authentication and certificate functions. I think it would
> be greate to have that added to pyzmq without requiring yet another
> modul
ter executed code that pyzmq does in
> compiled C code, compiling away the interpreter and there is no doubt in my
> mind that pyzmq is faster. pyczmq is not an attempt by me to replace pyzmq
> or supersede it in any way, my primary goals were to 1) learn CFFI, 2)
> evaluate
ffi<http://cffi.readthedocs.org/en/latest/index.html?highlight=get_extension#distributing-modules-using-cffi>.
PyZMQ does
this<https://github.com/zeromq/pyzmq/blob/f58bb80b3b7583fb45824d0a1037128f7f29d44a/setup.py#L1003>
for
its CFFI backend on PyPy, and it seems to work reasonably well.
don't think it would. Most of the things czmq adds to libzmq are more
logically reimplemented in Python, rather than exposed by linking anothing
library. The added C dependency would also be too much of a pain, given the
minimal benefit it provides at the Python level.
-MinRK
>
>
On Sun, Dec 29, 2013 at 12:09 PM, Min RK wrote:
>
>> what is zmq.zmq_version() on each?
>>
>> -MinRK
>>
>> On Dec 29, 2013, at 0:01, Thomas Johnson
>> wrote:
>>
>> Consider the following simple program:
>> #CUT HERE
>> #!/u
what C compiler do you have available? You may need to:
export CC=actual_c_compiler
because Python tries to compile extensions with the compiler used for
Python itself by default (often not available if cross compiled)
On Mon, Dec 9, 2013 at 11:15 AM, Roman wrote:
> Here is the output of runn
In general, you can use 0MQ 4 exactly the same as 3.2, there should be no
backward-incompatible changes, only new stuff. That's the goal, anyway,
obviously you have to give it a try to see how it goes in practice, but
it's been pretty solid in my experience thus far.
-MinRK
On Fri, D
nly useful if
that transaction is sufficiently rare, such as when blocking zmq calls are
a minority of your app's run time.
-MinRK
>
>Greg
> ___
> zeromq-dev mailing list
> zeromq-dev@lists.zeromq.org
> http://lists.zero
I also cut pyzmq-14.0.1 yesterday, which bundles 4.0.3.
On Sun, Nov 24, 2013 at 11:50 PM, Pieter Hintjens wrote:
> Hi all,
>
> There was a failing test case in 4.0.2 (error in a new test case, not
> the library), so we made a 4.0.3 release to fix that. Same place as
> usual. Sorry for the hiccu
On Tue, Nov 19, 2013 at 3:54 PM, Nikola wrote:
> Any pointers on how to make it static?
>
not that I am aware of, but it shouldn't be too hard to search for.
>
>
> On Wed, Nov 20, 2013 at 12:33 AM, MinRK wrote:
>
>> Yes and no - compiled Python modules are
Yes and no - compiled Python modules are themselves dynamic libraries,
so the best result is N-1 dynamic loads if you make libzmq static.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
First tnx for helping out.
>> Question is , can I make it so much portable to put it in my project
>> directory and just call import pyzmq and it will work?
>>
>>
>> On Tue, Nov 19, 2013 at 7:05 PM, MinRK wrote:
>>
>>> Add the flag `--zmq=bundled`, a
Add the flag `--zmq=bundled`, and pyzmq will compile libzmq as a Python
extension, and ship it. So for a fully portable pyzmq:
python setupegg.py bdist_wheel --zmq=bundled
should do it.
On Tue, Nov 19, 2013 at 1:08 AM, Nikola wrote:
> Hi,
>
>
> Is there option to make static build so that py
q-4.0?
-MinRK
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
125 consecutive test runs without failure and counting. Thanks guys!
On Wed, Nov 6, 2013 at 8:52 AM, Pieter Hintjens wrote:
> Ric, this is great! I'll backport the fix to 3.2 and 4.0 once MinRK
> confirms it.
> On Nov 6, 2013 4:55 PM, wrote:
>
>> Well, hopefully I
sight on what might be causing the problem, or how I might
dig deeper into more useful information?
-MinRK
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
e. I might just be doing something dumb, though...
>
> Thanks for looking into it.
> --ap
>
>
> On Wed, Oct 16, 2013 at 12:52 AM, MinRK wrote:
>
>> What version of pyzmq? Can you provide a complete failing example? I
>> can't reproduce t
What version of pyzmq? Can you provide a complete failing example? I can't
reproduce this in pyzmq master, so maybe I have fixed it since 13.0.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
x27;s
with metadata in Python, I would just use the keypair generation and a
Python dict, then serialize to whatever common format (yaml, json, etc.).
-MinRK
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/z
y ZAP
threads, etc.). I'm also working on a PR to put curve_keygen into
zmq_utils, so it is available to all bindings as a library function,
without having to wrap libsodium separately.
-MinRK
On Sat, Sep 28, 2013 at 2:20 PM, Thomas S Hatch wrote:
> I imagine I am missing something basic he
lose are no-ops if the process has been forked (no
libzmq API will be called). But no 'real' methods, where you are asking for
something to actually happen, are protected for performance reasons.
-MinRK
> I'm experimenting with a way of terminating the inherited context
On Fri, Aug 30, 2013 at 1:37 PM, Pieter Hintjens wrote:
> On Thu, Aug 29, 2013 at 1:32 AM, MinRK wrote:
>
> > Thanks. By closed, you mean the connecting peer (client) should be
> closed,
> > or the inner pipe on the server side? What should be the user-visible
&
On Fri, Aug 30, 2013 at 11:50 AM, Townsend, Scott E. (GRC-RTM0)[Vantage
Partners, LLC] wrote:
MinRK noted that:
>
> You cannot continue to use zmq sockets after a fork - you have to
> take care in your application that no sockets created before the fork will
> be [not be] used
You cannot continue to use zmq sockets after a fork - you have to take care
in your application that no sockets created before the fork will be used by
any calls in the child process.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.z
or should sending a message not succeed
in the first place?
-MinRK
> On Sun, Aug 25, 2013 at 8:51 PM, MinRK wrote:
> > Hello,
> >
> > I'm working on [adding support](https://github.com/zeromq/pyzmq/pull/401
> )
> > for 3.3 bits in pyzmq, and I'm testing the
kets.
I assume this is not intended. Is the implementation supposed to be
complete at this point? And what precisely should be the effect of a
failed authentication (i.e. which calls should raise, block, etc.).
Thanks,
-MinRK
___
zeromq-dev mailing
> you might want to look into the rpath linker option - in essence it gives
> you a way to bundle a library path with a binary
>
Ah yes, I forgot that I do this in pyzmq when I ship libzmq with it. The
distutils setting is `runtime_library_dirs`, and can include relative paths
(relativ
Depending on the nature of your code, it should be okay as long as pyzmq is
imported first, which loads the bundled libzmq into RTLD_GLOBAL if there is
one.
It is meant to support use from Cython, but I confess that I am only aware
of one such project (gevent-zeromq), which has since been absorbed
On Wed, Aug 7, 2013 at 3:57 PM, Bryan Richardson wrote:
> Thanks for the response MinRK. So are you saying I could build Python from
> source on a Windows machine using VS 2008, and then build the pyzmq MSI
> from source against the pre-compiled ZeroMQ library for Windows
> (libzmq-
I never made an MSI for 2.5, since it was deprecated before pyzmq had any
binary installers.
Note that you don't have to build pyzmq on the machine itself, you can run
`python setupegg.py bdist_msi` (or bdist_egg) on your own Windows machine
or VM, then pass that MSI to the target machine.
___
after 381):
mps: 110436
mps: 110876
mps: 104220
mps: 110690
mps: 100544
mps: 110922
-MinRK
On Mon, Jun 24, 2013 at 12:18 PM, Brian Knox wrote:
> Thanks Min - additionally if I'm incorrect in my assumption that the poll
> look in my example code should perform better, or if there&#x
I ran your tests on my Linux machine (amd64 Ubuntu 12.04, 12 GB RAM, i7
930),
in case you are interested in more numbers
(everything from git master)
jzmq:
It took 2.574 seconds to process 200 messages of size 10 Byte(s) in a
batch
777000.7770007771 messages/second
It took 1.856 seconds to p
(EINTR) should happen. This was broken
in 13.0.0, but is fixed in master.
13.0 was a big release, and there are unsurprisingly a few bugs. There
will be a bugfix release around 30 days after the original (about two weeks
from now).
-MinRK
On Mon, Mar 11, 2013 at 2:16 PM, Min RK wrote
rror:
> cython=False
>
> Cheers!
>
>
> --
> From: benjami...@gmail.com
> Date: Fri, 22 Feb 2013 08:54:38 -0800
> To: zeromq-dev@lists.zeromq.org
> Subject: Re: [zeromq-dev] pyzmq build fails ?
>
>
> What Cython version? try updating it.
&g
es.ThreadProxy/ProcessProxy`.
>
> Brian
>
>
> On Thu, Feb 21, 2013 at 7:27 PM, MinRK wrote:
>
>> pyzmq 13.0.0 released, with bdists bundling libzmq-3.2.2.
>>
>> Main new feature is support for pypy via added CFFI backend.
>>
>> _
pyzmq 13.0.0 released, with bdists bundling libzmq-3.2.2.
Main new feature is support for pypy via added CFFI backend.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Minor Cython tweaks for rc3:
pip install
https://dl.dropbox.com/sh/nsww1t3adru9p3o/OD_MslRnkB/pyzmq-13.0.0-rc3.tar.gz
All RCs here: https://www.dropbox.com/sh/nsww1t3adru9p3o/JvkcvlOcxA
I expect this to be the last one before 13.0 release this week, unless I
hear about issues.
-MinRK
On Sat
Some more build fixes for RC2:
pip install
https://dl.dropbox.com/sh/nsww1t3adru9p3o/E1p1gyK8eG/pyzmq-13.0.0-rc2.tar.gz
All RCs here: https://www.dropbox.com/sh/nsww1t3adru9p3o/JvkcvlOcxA
-MinRK
On Tue, Feb 5, 2013 at 1:01 PM, Brian Knox wrote:
> That did the trick!
>
>
> O
Gotcha, 'by hand' doesn't invoke setuptools, so dependencies are ignored.
That's to be expected. `python setupegg.py install` will run setup with
setuptools, invoking the dependency stuff.
>
>
> Brian
>
>
> On Tue, Feb 5, 2013 at 12:34 PM, MinRK wrote:
>
&
e?
>
How did you install the RC?
the CFFI backend has a few dependencies:
pip install py ctypes-configure cffi
They should be pulled in if you install with pip/easy_install. Let me
check if I messed that bit up.
-MinRK
>
> Thanks!
>
> Brian
>
>
> On Mon, Feb 4, 2013 at 8
t
found at build time)
Change notes: http://zeromq.github.com/pyzmq/changelog.html
Please do let me know if you have any build issues, because that part of
the code is far from awesome.
-MinRK
___
zeromq-dev mailing list
zeromq-dev@lists.zerom
On Fri, Jan 18, 2013 at 12:01 AM, Pieter Hintjens wrote:
> On Fri, Jan 18, 2013 at 1:16 AM, MinRK wrote:
>
> > For instance, what would we do if there ever needs to be a context option
> > that isn't an int?
>
> In theory, using macros and a single function makes
1 - 100 of 289 matches
Mail list logo
