Azure support - use same ENV names as python-openai#26
Merged
Conversation
npiv
approved these changes
Mar 27, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 makes chatblade use the same ENV variables that openai-python already supports:
OPENAI_API_ENDPOINTtoOPENAI_API_BASEOPENAI_API_TYPE=azure.Note that the engine name setting is still required.
Comment on chat.py:84 -- In the current openai the default openai.api_version does not work with the Chat API on azure, so need to override. Once openai/openai-python#335 is released that workaround can be removed, and we only need the engine setting.