Skip to content
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

Dependancies are too restrictive #47

Closed
benoit-cty opened this issue May 21, 2024 · 1 comment · Fixed by #48
Closed

Dependancies are too restrictive #47

benoit-cty opened this issue May 21, 2024 · 1 comment · Fixed by #48

Comments

@benoit-cty
Copy link

Describe the bug

Hello, I'd like to use EcoLogits in a project using LangChain. But it's impossible because EcoLogits prevent to use packaging>=25.0

If you did not need specific version of a package, I think it's better to remain open to all versions.

To Reproduce
Steps to reproduce the behavior:
poetry add ecologits langchain-core

Because no versions of ecologits match >0.1.5,<0.2.0
 and ecologits (0.1.5) depends on packaging (>=24.0,<25.0), ecologits (>=0.1.5,<0.2.0) requires packaging (>=24.0,<25.0).
Because langchain-core (0.1.52) depends on packaging (>=23.2,<24.0)
 and no versions of langchain-core match >0.1.52,<0.2.0, langchain-core (>=0.1.52,<0.2.0) requires packaging (>=23.2,<24.0).
Thus, ecologits (>=0.1.5,<0.2.0) is incompatible with langchain-core (>=0.1.52,<0.2.0).
And because langchain-experimental (0.0.58) depends on langchain-core (>=0.1.52,<0.2.0)
 and no versions of langchain-experimental match >0.0.58,<0.0.59, ecologits (>=0.1.5,<0.2.0) is incompatible with langchain-experimental (>=0.0.58,<0.0.59).
So, because fiscal-qa depends on both langchain-experimental (^0.0.58) and ecologits (^0.1.5), version solving failed.
@samuelrince
Copy link
Member

Thanks for reporting @benoit-cty! Looking into it, the fix should be published very soon in the release 0.1.6! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants