Replies: 1 comment
-
|
Another thing to consider related to this: the use of a |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
I currently have
requirements.inandrequirements.txtfiles that are used in combination withpipandpip-toolsto manage project dependencies and installed dependencies in various environments.One nice thing about using
pip-tools'spip-compilecommand is that you no longer have to ensure all dependencies of the top-level dependencies are installed and at the correct version. Instead, you only specify the top-level dependencies inrequirements.inand then compile the more detailedrequirements.txt.While this is arguably superior to having a single, manually-maintained
requirements.txtfile, it still feels overly complicated.I have read suggestions to use a metadata-driven approach via
setup.cfgorpyproject.tomland maintain the top-level dependencies there. I think this would be a positive change, as it would eliminate the need to compile the second file. Dependabot should still be compatible with projects managing dependencies viasetuptools.References
Beta Was this translation helpful? Give feedback.
All reactions