Reason: --autoresolve will not work with our nightly builds. It will for example use scipp @ https://github.com/scipp/scipp/releases/download/nightly/scipp-nightly-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl in all .txt files.
Why did it work before?
I think that pip-compile-multi will make sure that any .txt file it makes is consistent, so if test.in depends on base.in and there is a package in base.in and another in test.in that both request the same dependency, it will ensure the version is consistent. It will however not check globally for consistent version across all files.
Why were we getting errors before?
If there is a file dev.in that depends on both docs.in and test.in, but docs.in and test.in are unrelated
It could be that test.txt resolved some-package==4.0 and docs.txt has some-package==3.8.
An error is raised in that case.
When using --autoresolve and a single file that contains all the dependencies, pip-compile-multi starts by resolving that file, before it does all the others.
Essentially revert #106
Reason:
--autoresolvewill not work with our nightly builds. It will for example usescipp @ https://github.com/scipp/scipp/releases/download/nightly/scipp-nightly-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whlin all.txtfiles.Why did it work before?
I think that
pip-compile-multiwill make sure that any.txtfile it makes is consistent, so iftest.independs onbase.inand there is a package inbase.inand another intest.inthat both request the same dependency, it will ensure the version is consistent. It will however not check globally for consistent version across all files.Why were we getting errors before?
If there is a file
dev.inthat depends on bothdocs.inandtest.in, butdocs.inandtest.inare unrelated It could be thattest.txtresolvedsome-package==4.0anddocs.txthassome-package==3.8. An error is raised in that case.When using
--autoresolveand a single file that contains all the dependencies,pip-compile-multistarts by resolving that file, before it does all the others.