Timeout for ModbusUdpClient about pymodbus HOT 5 CLOSED

I am fine adding this, but I will keep the default set to None. As for the python3 branch, I know a few groups who are using it, but I believe only for TCP async clients. Ideally I don't want two branches (just one), but I have been wary to pull the switch quite yet without more people trying it out and reporting their results on both 2.7> and 3.x.

from pymodbus.

Thanks for considering this for integration. Default to None is fine. Regarding Python3: the modbus lib is the final lib blocking the move of my open-source roasting app Artisan to move to Python3. I used the minimialmodbus lib up to now exactly for its Python3 compatibility, but then wanted to add TCP/UDP support and moved to pymodbus as I saw and tested successfully the Python3 branch. Then I discovered the timeout issue on UDP and could solve it only nicely by some monkey patching (class overwriting) and parameter passing (only available in the latest version and not the Python3 branch).

So for me the Python3 branch worked as expected (mostly tested the RTU and UDP part) and I would vote for ONE branch that supports both Python version.

from pymodbus.

Upps. Note that behind myTonino and MAKOMO is the same person, me. Thanks for giving us pymodbus!

from pymodbus.

Fixed with b13c89d

from pymodbus.

I believe the modification above has not been committed properly. It should read, as MAKOMO suggested:

self.socket.settimeout(self.timeout)

but it appears to have been commited as:

self.settimeout(self.timeout)

which deliver a no method error in case the timeout option is passed.

from pymodbus.