try to fix pygbag failing when --help passed #205
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.
pygbag errors with codes 89 and 83 when called with just
--help
.This may be confusing. Command line programs usually do not fail when called with just
--help
, even if they usually require other arguments on standard runs.I did some digging, and pygbag first processes args with
set_args
, failing if the app folder or other metadata could not be found. Then, it callsmain_run
. This means if we create our parser inmain_run
, we will fail even if we just runpygbag --help
. Thus, I created aget_parser
function that can be called withget_parser(None, None, None, None)
inset_args
when--help
is in the command line arguments, to parse it to print out help data and then exit.This might work, but might not. I didn't figure out how to run pygbag locally, so the coding was done a bit blind.