Skip to content
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.

Fixed compatibility with websocket-client callbacks [see #173] #174

Merged
merged 2 commits into from
Apr 8, 2021

Conversation

blacklight
Copy link
Contributor

The websocket-client callbacks, as of 0.58 (01c791c),
require the websocket application object as first argument. Since things are the
other way around for websocket-client >= 0.53.0, and yet the other way around on
previous versions, this commit is supposed to stop the madness around
websocket-client callbacks with a dynamic list of arguments.

  • Fixed docstring for the Listener object.

  • Fixed list of arguments inherited by run_forever.

…tter#173]

The websocket-client callbacks, as of 0.58 (richard-better@01c791c),
require the websocket application object as first argument. Since things are the
other way around for websocket-client >= 0.53.0, and yet the other way around on
previous versions, this commit is supposed to stop the madness around
websocket-client callbacks with a dynamic list of arguments.

- Fixed docstring for the Listener object.

- Fixed list of arguments inherited by run_forever.
@rbrcsk rbrcsk merged commit 5d9ad10 into richard-better:master Apr 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants