-
Notifications
You must be signed in to change notification settings - Fork 73
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
docs(weave): Update docs to reuse the new method for initializing the cohere_patcher #3326
Conversation
This PR requires manual approval from a wandb user to run all CI checks. To see the current diff, click here. To approve CI for this PR as of this commit, comment:
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=546c8c1c1f5478e80259aef972e476c77e6047ac |
Commit (wandb@adb740b) introduced a change that moved the cohere patcher initialization to a method: get_cohere_patcher. This resulted in a error accodring to the Cohere integrations docs which counted on the weave.integrations.cohere.cohere_sdk to provide "cohere_patcher" variable.
1a2fa96
to
0a9f18e
Compare
/approve 0a9f18e |
Thank you for the excellent PR description! |
Our CI system doesn't work with branches in forked repos so I cloned this and merged it separately. Thank you for the contribution! |
Description
Use the new method for initializing the cohere_patcher
What does the PR do?
This PR introduces a small change that makes use of the new method for initializing the cohere_patcher and reflects
Commit (adb740b) that moved the cohere patcher initialization to the following method: get_cohere_patcher and away from using directly the cohere_patcher variable. Without this PR if a user follows the cohere integration docs it will face the following error
ImportError: cannot import name 'cohere_patcher' from 'weave.integrations.cohere' (/usr/local/lib/python3.10/dist-packages/weave/integrations/cohere/__init__.py)
Testing
How was this PR tested?
Tested locally by running the following code in a Notebook: