Skip to content

Conversation

@mweinelt
Copy link

The client, server, protocol, and auth modules were moved from the websockets package to websockets.legacy sub-package, as part of an upcoming refactoring. Despite the name, they’re still fully supported. The refactoring should be a transparent upgrade for most uses when it’s available. The legacy implementation will be preserved according to the backwards-compatibility policy.

https://websockets.readthedocs.io/en/stable/changelog.html#id5

Fixes: #239

> The client, server, protocol, and auth modules were moved from the websockets package to websockets.legacy sub-package, as part of an upcoming refactoring. Despite the name, they’re still fully supported. The refactoring should be a transparent upgrade for most uses when it’s available. The legacy implementation will be preserved according to the backwards-compatibility policy.

https://websockets.readthedocs.io/en/stable/changelog.html#id5

Fixes: njouanin#239
@deztructor
Copy link

(Tested: it is working)

Copy link

@SylteA SylteA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works :)

@FlorianLudwig
Copy link
Contributor

FYI

hbmqtt is EOL.

#235

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue: ModuleNotFoundError: No module named 'websockets.protocol'

4 participants