You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, I tested and this seems to be the same behavior as pip-compile:
$ time pip-compile requirements.in --pip-args "--no-cache-dir" --output-file test_out2.txt --quiet --strip-extras
real 0m30.315s
user 0m12.760s
sys 0m0.456s
$ time pip-compile requirements.in --pip-args "--no-cache-dir" --output-file test_out2.txt --quiet --strip-extras
real 0m21.981s
user 0m7.968s
sys 0m0.471s
$ rm test_out2.txt
$ time pip-compile requirements.in --pip-args "--no-cache-dir" --output-file test_out2.txt --quiet --strip-extras
real 0m29.986s
user 0m12.799s
sys 0m0.400s
I even tested that it doesn't upgrade a valid solution, I just find this very unintuitive, as it's called an output file not a sync file, but it matches the tool you are mirroring so ¯\(ツ)/¯.
Python 3.10 uv 0.1.31
Create a requitement.in file as such:
No compile these requirements without cache to an output file, then again with the existing output file, then again without the output file:
What's going on here? Why would a file that you write to speed up resolution?
This might not be a bug but it feels wrong, it should be at least documented in the help which currently just says:
The text was updated successfully, but these errors were encountered: