Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Properly revert _app.py callback to state before PR #442 (previously …
…only partially reverted)
- Loading branch information
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's my understanding of the history of this callback code, so that you can point out what details I'm missing:
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI it broke compatibility with Pysher 1.0.6 deepbrook/Pysher#62
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It broke usage of WebSocketApp without inheritance:
Error: error from callback <bound method JsonWebsocket._on_open of <JsonWebsocket object at 0x000001FBAF9D90B8>>: _on_open() takes 1 positional argument but 2 were given
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not actually this commit that broke it but this one: 40e3a93
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@engn33r hey there, I'm trying to make SignalRCore module work with websocket-client newer than 0.54.0 but having rolled back to how it was prior to #442 broke compatibility. Why not keep this code:
If I bring it back in 0.59.0, everything works perfectly (at least for the module I'm trying to upgrade.
Does it causes issues that I'm not aware of?
Thanks for maintaining this module btw!
3112b7d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@morpheus65535 This is a known issue, see #669 and the duplicate issues referenced within. Release v0.58.0 introduced a breaking change and was not numbered following semver. The 1.0.0 release transitions the project to use semver properly.