test: use send
, not sendto
on connected socket
#87
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #86.
According to the Python docs
(https://docs.python.org/2/library/socket.html#socket.socket.sendto),
you should not use
socket.sendto
if a socket is already connected.Linux (Ubuntu 12.04) seems to be forgiving of this behavior, but when I
run tests on OSX, I get several
socket.error: [Errno 56] Socket is already connected
errors in the test suite.This behavior can be demonstrated with the following Python script:
On Linux, this works and the received messages are printed.
On OSX, the
sendto
calls raises aSocket is already connected
error.