Skip to content

Pinned down websocket-client==1.1.0 #810

Closed

Description

@nbmurphy

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

Activity

  1. cdce8p commented on Jan 13, 2022

    @cdce8p

    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

  2. stale commented on Apr 17, 2022

    @stale

    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.

  3. cdce8p commented on Apr 17, 2022

    @cdce8p

    This is still an issue

  4. added a commit that references this issue on Apr 17, 2022
  5. epenet commented on Jan 21, 2023

    @epenet

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

  6. rutkai commented on Apr 27, 2023

    @rutkai

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

  7. arne-kapell commented on Aug 2, 2023

    @arne-kapell
    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.

  8. added a commit that references this issue on Aug 4, 2023
    8e340d2
  9. added a commit that references this issue on Aug 7, 2023
    75432a6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions