Update the Semver Specifier for langchain to allow for all <0.1.0 versions.#86
Merged
ogabrielluiz merged 5 commits intoApr 27, 2023
Merged
Conversation
Contributor
|
Hey. Sorry for the delayed response. We might get errors because a person is using a different version than what is intended. What do you think? |
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
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'm trying to install this in a project, and I noticed that poetry can't resolve this with the latest versions of langchain. The issue is that with the
^specifier on a patch-only version, it will only allow a single patch - so this is effectively '>=0.0.113;<0.0.114. By using~` here for the time being, we can allow for more recent versions.