2015-05-30, 23:34
I've pushed v1.9.5 which should fix this, it's actually a problem with Python 3.3 (and maybe earlier, but not Python 2.7.x), which doesn't like the last exception - in this case, socket.error("timed out") - to be raised once the exception has gone out of scope... at least, that's the best way I can describe it. The fix is fairly easy, just make a note of the last exception so that it remains in scope... a bit hackish, but meh.