-
Notifications
You must be signed in to change notification settings - Fork 301
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
Refactor Python dependencies into multiple files depending on app #6750
Comments
For historical context - the dependencies were initially in separate files, but they were collected in a single |
Could be worth using More info here: https://stackoverflow.com/questions/66751657/what-does-pip-compile-do-what-is-its-use-how-do-i-maintain-the-contents-of-my |
…rements directory; rucio#6750
…rements directory; rucio#6750
…rements directory; rucio#6750
…rements directory; rucio#6750
…rements directory; rucio#6750
Description
To meet this request: #6663
We agreed to split the single
requirements.txt
file into multiple files. For the client, the dependencies should be unpinned (as the client is used as a library in certain use cases), whereas we should keep all dependencies pinned for the server.Motivation
No response
Change
No response
The text was updated successfully, but these errors were encountered: