'websocket' clashes with other popular python libraries

[mtford90]

''websocket' is quite a generic, all-encompassing name for a package that is only a client and causes issues when using other websocket libraries (.e.g. those that provide a server implementation) in the same python installation.

[liris]

Well...
It's too late to change module name....

change module installation environment by virtualenv or something like that....

[engn33r]

I understand websocket is quite generic, but I am not aware of a solution to this currently that could change the name without impacting all projects using websocket-client as a dependency. If you know of solution, please share and we can consider whether a name change is worth the effort. Closing as won't fix due to lack of a clear solution.

[hughperkins]

Make the name change in a major version upgrade.

Existing users will be version locked to the current major version. They can choose to upgrade to the new major version if they wish, at which point they will change the imported name.

[hughperkins]

(I mean, in general, myself, and people around me, put things like this in requirements files:

some_package >=1.5.7,<2.0.0

)

[engn33r]

Reopening because the idea of changing the name to "websocket-client" on a future major version upgrade is a good idea for the long term, even if it causes some confusion in the short term