Retry on EINTR error

For whatever reason ZMQ now raises ZMQErrors with an errno.EINTR code.
We simply retry when they occur.

fixes #62
Fix a broken unit test

For who is intersted by the resolution:
 - a channel cannot be considered opened until the endpoint answered
 - the code was sending 2 events in a row...
 - the first event will open the channel
 - but if the second event arrive "too fast", the channel wont be "fully
   opened"

The solution:
 - wrap the channel in a BufferedChannel, which automatically prevent
   sending more than one message until the channel is opened fully.
bump version to v0.4.2
EINTR, EINTR eveywhere!

for some reason, zmq thorw EINTR on getsockopt calls now...
ref #62
bump version to v0.4.3
the latest zerorpc code needs at least pyzmq 13
Merge pull request #64 from jpetazzo/fix-pyzmq-dependency

the latest zerorpc code needs at least pyzmq 13
fix tests

event args were expected to be tuples, but they are lists
use logging instead of printing to stderr
Issue #74 retry connect and getsockopt on EINTR

Conflicts:
	zerorpc/gevent_zmq.py
Merge pull request #68 from Infinidat/logging

use logging instead of printing to stderr
tests - support event.args as both tuple and list
Merge branch 'dotcloud-master' of git://github.com/Infinidat/zerorpc-python into Infinidat-dotcloud-master

Conflicts:
	zerorpc/gevent_zmq.py
Merge pull request #67 from Infinidat/testing

fix tests
Fix messed up indentation
Pin pyzmq==13.1.0 because 14 BREAKS ALL THE THINGS.
bump version to v0.4.4
Additional fixes for Issue #41

Issue #41 was about an `zmq.core.error.ZMQError: Invalid argument` error when trying to connect to `tcp://*:4242`, however I ran into the same bug in Ubuntu 13.04 connecting to `tcp://:4242`.
Merge pull request #78 from jgeewax/patch-1

Additional fixes for Issue #41
Fixed deprecation warnings:
gevent.queue.Queue(0) now means infinity queue, changing to Channel instead.
gevent.coros module deprecated in favor of gevent.lock