Loosen packages version range specifications #1525
Gael Grosch (Digma)
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Many of us have encountered the "dependency hell" that comes with Python projects, especially when integrating with various services or framework. Graphrag is very strict in term of dependency version even for stable projects like
pandas = "^2.2.3",matplotlib = "^3.9.3",pyyaml = "^6.0.2",httpx = "^0.28.1", ...While we try to keep our dependencies up-to-date, we depends on other project which can not always be as reactive bumping up version numbers. In our case, the very strict graphrag restrictions are conflicting with multiple other libraries like Prefect, Supabase or GCP.
We would like to open a discussion regarding loosening up the package restrictions which we feel make integrating graphrag into real project difficult.
The first question would be: What is the rational behind only accepting the very latest release of projects when there has no been no minor/major bump or breaking changes?
All reactions