fix: pin compatible dependency versions in root requirements.txt - #227
Open
Shrishagk wants to merge 1 commit into
Open
fix: pin compatible dependency versions in root requirements.txt#227Shrishagk wants to merge 1 commit into
Shrishagk wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR pins compatible versions for the dependencies in the root
requirements.txt.Although #212 resolved dependency resolution issues for
api-service/requirements.txt, the rootrequirements.txtstill contains unconstrained LangChain dependencies. On a fresh virtual environment, running:causes pip to spend a long time backtracking through multiple versions of the LangChain ecosystem before failing or taking an excessive amount of time.
This PR updates the root dependency versions to a tested, compatible set.
Related Issue
Fixes the remaining dependency resolution problem in the root installation path.
Motivation
The project README instructs users to install dependencies using the root requirements.txt. Since the dependency versions were largely unpinned, pip attempted to resolve many incompatible combinations.
Pinning compatible versions makes installation deterministic and allows a fresh setup to complete successfully.
Tested
Windows 11
Python 3.11.8
Fresh virtual environment
pip install -r requirements.txt completes successfully
Application starts successfully after installation