TypeError with -r, -s, and -S options about rivalcfg

[flozz]

I will try to fix that Monday or Tuesday, and I will add some tests to automatically check that everything work on Python 2 and Python 3

[flozz]

I am not able to reproduce this bug (I tested with Python 2.7 and Python 3.5 on Ubuntu).

• Are you able to reproduce with the latest commit from master?
• What is your exact Python version python --version?
• What is your Linux distribution?

Are you able to reproduce with the latest commit from master?

Yes. Updated to r67.71e0b62 and produces the same message.

What is your exact Python version python --version?

Python 3.5.2

What is your Linux distribution?

Arch Linux. Output from uname: Linux janus 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux

[flozz]

I will install an Archlinux VM to try to reproduce

[flozz]

Hello,

I installed rivalcfg using your AUR package, I tested in DEBUG_DRY mode and it worked fine, but the problem seems to happen when the application tries to write informations to a real device. I will have to wait until tomorrow to test on my own Rival 100.

Could it be an issue with pyudev?

[flozz]

I tried with the real mouse plugged in, and it worked fine... I cannot figure out what is going wrong... That is a weird issue :(

Could it be an issue with pyudev?

It should not, because it is used only to find devices, not to send data to mice.

[flozz]

Oh! I think I found the problem... With Python 3, rivalcfg tries to write floating point numbers to the devices (only for Rival and Rival 300). Can you confirm that the last commit fixes the issue?

rivalcfg tries to write floating point numbers

I suppose TypeError: an integer is required indicates this.

Can you confirm that the last commit fixes the issue?

r68.09e6ef8 fixes the issue. Great work! 👍

[flozz]

rivalcfg 2.4.3 released with this issue fixed :)