-
Notifications
You must be signed in to change notification settings - Fork 761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebsocketApp does not identify callback arguments correctly on 0.49.0 #463
Comments
I'm experiencing the same issue trying to use the certsteram library and I originally opened this issue, CaliDog/certstream-python#18, there since I thought the problem might lie in that end. However, your issue seems to be very similar and downgrading to 0.48.0 sorts it for me as well. I saw that @nlevitt opened this pull request, #462, which sounds like it might address this issue. I tried to apply it manually and re-installed the websocket library but it didn't solve it in my end. Have you tried that fix yet? |
I just tried with the newly pushed version 0.50.0 and certstream and the problem persists there. @SparkyTheAlbino - does that version make any difference in your end? |
certstream subclasses WebSocketApp. It appears that #442 was intentionally a breaking change for this use case. In other words, it looks to me like certstream needs to migrate to the new api or pin to websocket-client<=48.0, unless @liris and @bashlakov change their mind about #442.
|
I’m thinking it is better to revert these changes because of breaking the compatibility. |
Using:
Python Version: Python 3.4.2
OS: Raspian Lite (Raspberry Pi Model 3B+)
When using the latest version 0.49.0 on_open, on_error, on_close all cannot see the args and therefore breaks everything and not connecting at all.
Downgrading back to 0.48.0 works fine, have been running this on another raspberry pi for quite some time now. Downgraded this new Raspberry pi to 0.48.0 and its working fine.
Here are few snippets from my code that may help:
The text was updated successfully, but these errors were encountered: