Pythonping

It is now possible to run a ping sweep by specifying only the sweep start size and the sweep end size, without hardcoding a static size. Previously it was necessary to manually set size to None for sweep settings to be considered, now if they are set size is ignored. This is not a breaking change as setting both sweep size and static size makes no sense and has no use case.

Special thanks to xalier1 for raising issue 64, now closed with this release.

Thanks to samgomena, we now have statistics on packet loss!
To get this statistics, simply access the `packet_loss` property on the Reponse List (the object returned from ping). A value of 1.0 represents 100% of packets lost, while 0% represents no packet lost.


python
rs = ping('127.0.0.1', verbose=True)
rs.packet_loss

This release fixes the [Python Issue 30482](https://bugs.python.org/issue30482) that made the underlying `socket.getprotobyname()` unreliable, as detailed in PR #56. Thanks to malbers15 for the fix.

Recent changes broke compatibility with python3.5, this release restores the compatibility.

- Restored full python3.5 compatibility (thanks to malbers15 for the quick fix)
- Improved docs for tiemout parameter (thanks to petermeissner, and also to malbers15 for reviewing the change)

Quick fix to issue 48 (consequence of code fixing issue 39). Thanks to malbers15 for quickly drafting the code for the fix.

As detailed in issue 48, the bug made all pings fail when they were using matching (legacy behaviour used for standalone run) was not impacted.

This release makes pythonping thread-safe. It does so by verifying payloads and generating different packet identifiers for each thread. In this way, multiple instances of pythonping can run in parallel in separate threads, as they are now able to filter out the responses meant to be received from that specific thread.

* Solved issue 39 specific about collisions with threads
* Solved issue 41 multi-thread support

A special thanks goes to deltaflyer4747 to clarify and identify the issue, and most importantly to malbers15 for actually writing the code to fix it!