feat: add the option for multiple --only flags.#4477
feat: add the option for multiple --only flags.#4477ruben-arts merged 4 commits intoprefix-dev:mainfrom
--only flags.#4477Conversation
This seems like it would need the warning of the mistake in the CLI. |
I think that should error? |
|
@lucascolley @ruben-arts I'd be fine, the only case I can think against it is that it is not really an error? As there is nothing wrong with it per se. A reason could be that you might have a bash script that does a loop over environments that it installs, and then it would be annoying if this is an error. Thats the only thing I can think of. Can I do this in a subsequent PR, as this is the behavior that is currently in main as well, and I dislike doing the changes in the same PR if can be avoided. |
|
sure, happy for it to be a warning instead |
It seems that the explicit exclusion ( |
|
Yeah there is some special logic that Python is always included when targeting PyPI packages maybe something is off there. This feature was a tad more complex than I initially envisioned 😅 |

This augments the abilities introduced in #4404, with the ability to do multiple
--only, before only one--onlyflag was accepted. In the end the technical change for this was pretty easy, we just add multiple starting points to the reachability analysis instead of one single root. These will then all be iterated through at some point.An additional thing that was added is a test to verify that
pixi install --only a --skip-with-deps askips the package. Something I felt was missing from the original test-suite.Tested
For
pixi.toml: