jolly-midnight-7275912/01/2020, 5:24 PM
? We want to put the minimal number of items in our constraints file as possible but we don't want to innundate people with these warnings.
[WARN] Ignoring resolve_all_constraints...
hundreds-father-40412/01/2020, 5:27 PM
work? I’m honestly not certain - we’ve only used it for deprecations. If it doesn’t work, we should fix that
We want to put the minimal number of items in our constraints file as possibleWarning that this means we can’t apply a huge performance optimization to use a single resolve for your tests and
. You’ll end up needing to resolve requirements a lot more than normal, which is often the most expensive step
jolly-midnight-7275912/01/2020, 5:30 PM
helpful-lunch-9208412/01/2020, 5:30 PM
hundreds-father-40412/01/2020, 5:34 PM
targets too https://www.pantsbuild.org/v2.2/docs/python-third-party-dependencies#tip-set-up-a-virtual-environment-optional
There is a possible issue if you have incompatible requirements - those would need to be manually resolved, unfortunately, e.g. deleting the version you don’t want. It’s possible to, say, use the global resolve for 90% of your code, and still have some other places that diverge from it. When it diverges, you’ll get this warning and you’ll do the proper resolve, rather than the global resolve
One of the biggest feature requests for Q4 is to support multiple constraints files
helpful-lunch-9208412/01/2020, 5:34 PM
and while the output is a little gnarly we could grep out the pip compatible package.
But that doesn’t seem to work in v2
./pants dependencies 3rdparty/python:mock
hundreds-father-40412/01/2020, 5:35 PM
to do the same thing. Which is a total misnomer. It really should be
./pants dependencies --type=3rdparty
or something like that
./pants dependencies --3rdparty-type=requirement_string
helpful-lunch-9208412/01/2020, 5:35 PM