Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Pinned down websocket-client==1.1.0 #810

Closed
nbmurphy opened this issue Dec 1, 2021 · 6 comments · Fixed by #833
Closed

Pinned down websocket-client==1.1.0 #810

nbmurphy opened this issue Dec 1, 2021 · 6 comments · Fixed by #833

Comments

@nbmurphy
Copy link

nbmurphy commented Dec 1, 2021

I work on a Speech Science software development team at CaptionCall. We have developed a system that can run audio through a selection of various speech-to-text ASRs --- including your ibm-watson recognizer. A pip requirement for your recognizer is websocket-client==1.1.0, pinned to one value. Other recognizers allow for a range of values which adds to the flexibility of our software system, enabling multiple recognizers to be selected during one run, without having to change software environments multiple times.

Here's an example of one such conflict:

ERROR: Cannot install -r requirements_benchmark_asrs.txt (line 10) and rev-ai==2.13.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    ibm-watson 5.3.0 depends on websocket-client==1.1.0
    rev-ai 2.13.0 depends on websocket-client<1.0.0 and >=0.56.0
@cdce8p
Copy link

cdce8p commented Jan 13, 2022

We at Home Assistant are having a similar issue. Pinned to ==1.1.0 doesn't really work unfortunately.
Would love an update here to open that up, ideally to at <1.3.0. The changelog seems to indicate that it should be compatible. websocket-client - ChangeLog

@stale
Copy link

stale bot commented Apr 17, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Apr 17, 2022
@cdce8p
Copy link

cdce8p commented Apr 17, 2022

This is still an issue

@stale stale bot removed the wontfix label Apr 17, 2022
wwwehr added a commit to wehr-enterprises/python-sdk that referenced this issue Apr 17, 2022
@epenet
Copy link

epenet commented Jan 21, 2023

This is still an issue: home-assistant/core#86336

@rutkai
Copy link

rutkai commented Apr 27, 2023

@apaparazzi0329 could you please advise on this issue? It'd be great to have a solution for this fixed version.

@arne-kapell
Copy link
Contributor

Still an issue for the same reason (homeassistant integration). As this seems to be noticed for almost 2 years now and regarding the presumably low effort for a fix this should be done soon.

arne-kapell added a commit to arne-kapell/watson-python-sdk that referenced this issue Aug 4, 2023
fixes watson-developer-cloud#810 and adds support for up to latest websocket-client (1.6.1)
apaparazzi0329 pushed a commit that referenced this issue Aug 7, 2023
fixes #810 and adds support for up to latest websocket-client (1.6.1)
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

5 participants