Allow for extra arguments to hatchling build #1743
Open
Conversation
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
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.
I was writing a custom hatch hook based off hatch-jupyter-builder, and I wanted to have behavior similar to their
--skip-npmflag. But I realized. that I cannot pass this flag to e.g.hatchling build!So this PR makes a small tweak to only parse out the known commands, leaving anything after the
--. If other unknown commands are mixed in, the same behavior as current should occur (print usage message, exit 1).This might resolve some issues, or allow for alternative solutions to questions raised by @blink1073