-
-
Notifications
You must be signed in to change notification settings - Fork 646
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A --resolve flag, to specify the resolves to export. (Cherry-pick of #…
…17416) (#17461) Currently, export takes cmd-line specs, so the python export implementation, which exports virtualenvs, exports the requirements of those targets. This has a couple of issues: A) User intent is almost certainly that export should emit the entire lockfile, whereas we will omit anything that isn't actively depended on by some target in the specs (which could be the case even with `::`). B) Tools don't relate to specs, so we export every tool every time, no matter the specs, which is obviously clunky. This change re-envisions how export should work. Instead of passing specs, you pass the `--resolve` flag one or more times, and we export a venv for each resolve, whether it's a user resolve or a tool resolve. The old codepath still works, but we can consider deprecating it in a followup. Closes #17398
- Loading branch information
Showing
6 changed files
with
261 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.