These errors were being caught by the original version of master, before Issue #283 was merged in.  Once realizing that the AttributeError on the _sock only occurred because we were calling client.parse_response instead of subclient.parse_response, it seemed most appropriate to revert to the way it was being handled originally.  

Obviously feel free to remove this if you do want to propogate the ConnectionError higher up.