-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Feature Request]: Better project dependency management #1052
Comments
The author of the discussion is here. Which project dependency management would the InfiniFlow/RAGFlow team prefer? I'm more experienced with Pipenv and less with Poetry. I don't mind learn another one if that is more suitable to your workflow. There is a comparison blog which you can reference. |
Let's use Poetry. |
Besides, is there any possibilities to separating the model provider and the main program into different projects, and provide a thin version of the program that only supports the OpenAI-like API? |
@KevinHuSh I will start working on it, no specific timeline though. Expect dependency version conflicts. |
Is there an existing issue for the same feature request?
Describe the feature you'd like
Discussed in https://github.com/orgs/infiniflow/discussions/1269
Originally posted by http403 June 1, 2024
Hi community and members of infiniflow,
Will the community be interested in pausing the development of RAGFlow a bit, and restructure the project using better dependency management tool? I'm trying to make the Docker image smaller by cutting out the GPU specific dependencies, which I use Poetry to aid me, and I discover few dependencies conflicts:
volcengine
needpycryptodome==3.9.9
gotpycryptodome=3.20.0
volcengine
needpytz==2020.5
gotpytz==2024.1
bcembedding
needtransformers>=4.35.0,<4.37.0
gottransformer==4.38.1
Note:
bcembedding
andvolcengine
aren't version pinnedIt will be nice to use some form of dependency management tools like Poetry or Pipenv to avoid such issues. Not to mention PyCryptodome 3.9.9 and
pytz
both released in 2020, which are very old which PyCryptodome have CVE-2023-52323 vulnerability before version 3.19.1.Again, I don't mind chime in my time to make it happen.
The text was updated successfully, but these errors were encountered: