feat(poly env): new command for build backends without support for multiple module roots or hooks #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Description
Adding a new command -
poly env setup- for Package & Dependency management tools without support for multiple module roots or hooks. This command will add the bases and components paths to the current virtual environment.Motivation and Context
See discussion #402
Users of
uvthat also use the uv build backend cannot set bases and components as module roots, or dev mode dirs as it is called in Hatch/Hatchling, because the uv build backend has no support for it. Also, his build backend has no support for hooks.Uv build backend users can now add the needed folders into the current virtual environment by combining the
uv synccommand with this new command:How Has This Been Tested?
✅ CI
✅ local run of the command
Types of changes
Checklist: