fix(azure): tolerate TranslatorCredential import changes - #102
Open
nateEc wants to merge 1 commit into
Open
Conversation
- Make TranslatorCredential a compatibility import instead of a startup requirement. - Fall back to the Azure Translator REST API when the SDK client cannot be created. - Normalize cognitiveservices endpoints for REST translate and language calls. - Verified with python3 -m py_compile app/abus_translate_azure.py.
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
1 participant
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.
Summary
TranslatorCredentiala compatibility import so app startup does not fail on SDK layout changes.*.cognitiveservices.azure.comendpoints for REST language and translate calls.Fixes #61.
Verification
python3 -m py_compile app/abus_translate_azure.py