Exception <class 'select.error'>: (4, 'Interrupted system call') after upgrading stompest

[tobgu]

After upgrading stompest from 2.1.6 to 2.3.0 I get 'Interrupted system call' whenever the application is waiting in canRead and I send a signal to the application.

I think this is due to the Python 3 updates here: 75c5692#diff-715c90981f31edb3e6e79120fa0c7e91L35

These types of exceptions were previously handled by stompest but I don't think that code is triggered anymore since if code == errno.EINTR is no longer true since code is no longer a number.

I'm running on Python 2.7.13.

[nikipore]

Thank you for your observation. Would you mind to contribute a fix, ideally including a test case (don't know whether mocking a signal is straightforward)?

[tobgu]

I can give it a try. Is python 3.3 compatibility a must? (This is handled by Python itself starting from 3.5).

[nikipore]

All support for the 3.3 series of releases ends on 2017-09-29, five years after the initial release, so we might drop 3.3 compatibility, but not 3.4. Would that help? If so, please do not forget to update the package metadata accordingly.

[tobgu]

It doesn't really help if we cannot also drop 3.4 support. I made an implementation for all three cases though.