On Sat, Feb 4, 2012 at 12:24 AM, john skaller <[email protected]> wrote:
> So? It would also mean I can run the tests, on practically any machine, > since Python is nice and portable (compared to C). Using PyZMQ as part of the libzmq "make check" process violates layering in quite a big way. At the same time John is right to suggest we're underusing PyZMQ in this capacity. It's clearly far cheaper to write test cases in Python than in C or C++. So the problem is that we need to run more tests on libzmq, more often, and we have excellent work that can do this but we're not using it fully. I can think of a few solutions: * Run the PyZMQ test scripts as part of the regular Jenkins build process * Carve off these test scripts as a more formal 0MQ test package that can be extended. * Start to create larger packages (libzmq + PyZMQ + CZMQ + jzmq + etc.) that can be tested together. Etc. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
