-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process wheelhouse.txt holistically rather than per-layer #569
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4624b5e
Process wheelhouse.txt wholistically rather than per-layer
johnsca 13f1a2d
Improve error handling
johnsca 2e9a4e3
Improve help text on --wheelhouse-per-layer flag
johnsca 09a2acf
Comment out overridden lines in wheelhouse.txt
johnsca 54e93ff
Fix test
johnsca File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-r and -R seem to be contradictory; how about we kill the -R codepath and just use -r=True|False instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to figure out a way to implement the
-r[=true/|false]
pattern but the case that always breaks is the current behavior that many may be using:There's no way with argparse to say "consume an arg, but only if it matches one of these choices". It will either not consume any args, always consume an arg, or try to consume an arg but blow up if it doesn't match one of the choices.
Additionally, I found at least one example with
git -p
andgit -P
which have the same contradictory meaning, and I know I've seen other cases and not found it terribly confusing. In general, and in the case of this change, the behavior is what I would expect: either of the options can be given, even multiple times, and the last one present on the command line takes precedence.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@johnsca i appreciate the attempt. I didn't intend for you to bend over backwards, but it sure would have been nice if "honor a bool value" would just work for argparse optargs. Anywho, I'm annoyed but not blocking contradictory flags; as you said, last in gets the cake, and i think that's a reasonable UX that charm builders can shoulder.
All that said, given that
--report
is now the default, I would ask you to consider #570. That is, deprecate-r
with some stderr message that says-r is default and therefore deprecated; use -R to prevent charm build reports
.