Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Compatibility Issue with OpenAI Whisper Implementation in openai>=1.0.0 #429

Closed
2 tasks
Ashesh3 opened this issue Jan 5, 2024 · 2 comments · Fixed by #466
Closed
2 tasks

Compatibility Issue with OpenAI Whisper Implementation in openai>=1.0.0 #429

Ashesh3 opened this issue Jan 5, 2024 · 2 comments · Fixed by #466
Assignees

Comments

@Ashesh3
Copy link
Member

Ashesh3 commented Jan 5, 2024

We are facing a compatibility issue with our OpenAI Whisper implementation. The current codebase attempts to use openai.Audio, which is no longer supported in the latest OpenAI Python library version (openai>=1.0.0).

Error Message:

You tried to access openai.Audio, but this is no longer supported in openai>=1.0.0 - see the README at https://github.com/openai/openai-python for the API. You can run `openai migrate` to automatically upgrade your codebase to use the 1.0.0 interface. Alternatively, you can pin your installation to the old version, e.g. `pip install openai==0.28`

Proposed Solutions:

  1. Automatic Codebase Upgrade: Run openai migrate to automatically update our codebase to be compatible with the openai>=1.0.0 interface.

A detailed migration guide is available here: OpenAI Python Migration Guide.

Action Items:

  • Review the migration guide and assess the scope of changes required for our codebase.
  • Implement the chosen solution and thoroughly test to ensure that our OpenAI Whisper implementation works seamlessly with the updated library.
@Ashesh3
Copy link
Member Author

Ashesh3 commented Feb 9, 2024

@ishanExtreme you mentioned that you were working on a fix for this issue, what's the status of the fix?

@ishanExtreme
Copy link
Contributor

@ishanExtreme you mentioned that you were working on a fix for this issue, what's the status of the fix?

Expected to fix it by today...

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 a pull request may close this issue.

2 participants