Make litellm version more flexible #1833
Merged
Conversation
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
Collaborator
|
Thank You so much for the contribution!! Yes the issue was with importing the caching module which kept breaking the test in CI. See: #1624 |
Contributor
Author
|
okay thanks! That's good to know. What do you think then moving forward, should we unpin as that issue was fixed? |
Collaborator
|
I think we can and iirc @chenmoneygithub checked the latest version and it was running fine. cc: @okhat |
isaacbmiller
pushed a commit
that referenced
this pull request
Dec 11, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
hey there!
I wanted to install dspy in a project where I also use litellm more explicitly, but unfortunately I couldn't update litellm version independently, I'm then adding the caret^ to flexibilize the minor version of it
now, that may be a risk as indeed I've seen litellm having quite few breaking changes in the past, @krypticmouse you were the one to change that from ^ to a explicit version before, do you remember what was the reason for that? f5a781c