updated openai to 1.1.1 #453
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Once this is merged, I can open another PR with initial support for |
That's awesome! |
As that branch depends on this one, I thought it would be better to wait a bit. But yeah, WIP PR sounds fine as well. |
This was referenced Nov 8, 2023
Merged
|
Thanks @gilcu3, I've bumped openai-python from 1.1.1 to 1.3.3 directly since there are no major changes involved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the minimal necessary changes to support the new version of the
openaipython library, specifically the current version1.1.1. I tested all the main functionality (private chats, group chats, plugins, images, transcription, stream) and it seems to work. I had my doubts on some functions in theutils.pyfile, please check those are used as expected before merging. Most changes done were related to changes on naming and the use of the newclientobject, and followed the migration guide here.Having this update I hope we will be able to use the new vision and TTS models soon :)