I'd also add some support for multiple sections in setup.py/setup.cfg (install_requires, tests_require, multiple extras_require) translating them (loosely) into in-files with additional constraints added for files already compiled (so that resolved versions are not conflicting). I guess the recompile approach with parsing output files should work for that as well as long as the order of compilation is preserved. Perhaps we could add some information on that into the same file header?

I originally posted a longer comment in #492 but that was before I read this discussion. I would like to somehow achieve both better setup.py parsing and multiple-in-files compilation as parts of the same generalized workflow.

UPD: I'm against using a makefile, I think this shouldn't depend on anything other than python and pip-tools. It could be a separate package, of course, but I think dependency layering is a common-enough practice that could benefit many pip-tools users if not most of them.

UPD2: We probably don't even need to add any custom header. If we have explicit -c lines we can use them to establish the dependency order of the files. I guess that's it, we just need the right way to add -c lines to inter-dependent in-files (that would be automated for setup.cfg) and a recompile script to go over the txt files and recompile them (in the correct order). And if the txt files are yet present we would just make some safe enough default assumptions and allow the user to run pip-compile manually for more granular control. Easy peasy, I guess I'll just start implementing it and stop bothering you guys :)

Uh oh!

support multiple requirements in / txt #532

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions