Right above the second time it prints, it prints the default usage line for that subcommand. When I call the one subcommand that has a required positional argument and I don't include that argument. When I call the main command and then type -help, the exact same thing happens as above. Also because the word usage appears in my text file, it says "usage: usage" When I call the main function with no subcommands and no arguments, my help_text from the text file outputs, and then like 2-3 additional lines of boiler plate I can't seem to get rid of. Lastly, I have set up a base case to display the help text whenever no subcommands are given. Before I reworked the help text, I had help text for each individual subcommand by using "help=" but now those are all blank. Only one of those subparsers has any additional arguments (one positional, one optional). Then I create subparsers (4 of them and then a base case) to create subcommands. I read in my help text file, set it to a string help_text, and then set "usage=help_text" on the parser. Here is the basics of how my program is broken down: But my boss isn't satisfied with the default help text, so he is having me write up the full usage/help text in a text file and just display the entire file.įor some reason, in a certain case, its outputting the text twice. ![]() Originally I had tried to leverage argparse's built in help text behavior. ![]() ![]() I created a command line interface with argparse. After an hour googling, I can't find anybody who has had anything resembling this issue besides myself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |