Deduplicate componentize-py dependency#101
Open
posborne wants to merge 2 commits into
Open
Conversation
Prior to this change, we had a verison of componentize-py that was mismatched from the version embedded in our own build tool. To avoid inconsistencies, we just expose the required bits of the `binding` subcommand we had been using with an entrypoint on our own CLI. End users will likely never need this, but it also is not harmful to ship either and unlikely to cause confusion.
These now match the implementation that was actually being provided at runtime (no functional differences).
erikrose
approved these changes
May 29, 2026
Member
erikrose
left a comment
There was a problem hiding this comment.
Sounds good. Yay for fewer things. Not too much of a maintenance burden.
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
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.
Prior to this change, we had a verison of componentize-py that was mismatched from the version embedded in our own build tool. To avoid inconsistencies, we just expose the required bits of the
bindingsubcommand we had been using with an entrypoint on our own CLI.End users will likely never need this, but it also is not harmful to ship either and unlikely to cause confusion.