0.1.5

What's Changed

• Compile armv7l wheels for more Python versions by @Lauszus in #17
• Use the extra index when building the armv7l wheels by @Lauszus in #18

Full Changelog: 0.1.4...0.1.5

0.1.4

• Go back to building the x86 wheels on Ubuntu 20.04

0.1.3

• Compile wheels for x86 Python 3.11, 3.12 and 3.13
• Compile wheel for armv7l Python 3.11
• Remove wheels for x86 Python 3.5, 3.6 and 3.7
• Remove wheel for armv7l 3.5

0.1.2

• Resolve data hang between CAN read and TCP write threads

0.1.1

• Disable Nagle's algorithm, so the CAN messages are not grouped together into one TCP packet

0.1.0

• It is now possible to forward a CAN socket to another machine via TCP. Fx forward can0 on the server to vcan0 on the client

0.0.7

• Return the correct error code if writing to a socket fails or it fails to initialize the read mutex

0.0.6

• Prevent absolute paths from ending up in the egg-info SOURCES.txt

0.0.5

• Fix all warnings
• Make all warnings into errors
• Fix printf warnings
• Redirect printf errors to stderr
• Make sure tcpclient is not blocking when it's waiting for a TCP connection
• The examples where not setting the hostname
• Expose the "is_alive" and "join" methods of the TCPClient process
• Only try to build the TCPClient extension on a Linux device
• Set an empty hostname by default

0.0.4

• Added some type hinting
• The read mutex was unlocked twice if poll was false
• Make sure the 'read_poll_tcp' thread is unblocked when the 'read_poll_can' thread exits
• Do not care about the data, when the 'read_poll_tcp' thread should exit
• Make sure 'socketcan_bytes_available' is initialized
• Do not use perror when printing the error code for a thread
• Make sure 'wait_rv' has been initialized if there has already been read a message before the thread has started. This caused the 'read_poll_tcp' to exit immediately