Issue #37 resolved

WebSocket receive() should never return None

lvella
created an issue

Instead of returning None, WebSocketError should be raised instead if receive() fails. The way it is now, I must treat 2 conditions that may overlap: catch WebSocketError and None returned, both means I must stop using the WebSocket.

Comments (2)

  1. Log in to comment