Closed tscheburaschka closed 9 months ago
@chrysle I have a problem with resolver
option for pip-compile. It fails for pip-sync.
Error: No such config key 'resolver'. Did you mean resolver_name?
But resolver_name
is an alias of resolver
option.
I found it handy to add some often used options to the
[tools.pip-tools]
-section of mypyproject.toml
. In particular I added:But now, calling
pip-sync requirements.txt
breaks with:I can see, that using instead
emit-index-url = false
would have the same effect and, actually, is probably the correct solution to this. But given the poor documentation of thepyproject.toml
-behaviour, we are left guessing and this is tedious and time-consuming. Moreover,pip-compile
does not complain about thepyproject
-options and happily uses them. Onlypip-sync
spoils the experience ;-) So, a bit more consistency would be nice.Environment Versions
Steps to replicate
no-*
options inpyproject.toml
, e.g.no-emit-index-url = true
pip-compile
and enjoy.pip-sync
and scratch your head, sort out your frustration and try to think, what could possibly be the issue here.Expected result
The behaviour of
pip-compile
andpip-sync
when using options frompyproject.toml
is consistent, well documented and intuitive.Actual result
The subset of options that work with
pip-sync
is unexpectedlty smaller than that ofpip-compile
.