Fix poly sync for PEP 621 build backends that isn't hatchling or pdm#438
Merged
Merged
Conversation
… using a build backend that isn't hatchling or pdm
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Fixing an issue with the
poly synccommand, when using a build backend that isn't Hatchling, PDM or Poetry.The way the command identified how to sync bricks didn't take other PEP 621-ready pyproject.toml files into account (such as when using the uv build backend).
Motivation and Context
To make it possible to sync bricks in development and in projects using
poly sync.How Has This Been Tested?
✅ CI
✅ Local testing of the poly sync command.
Types of changes
Checklist: