Скачать или смотреть Mixing Shared and Exclusive Arguments in argparse

Learn how to effectively use `argparse` in Python to share common arguments among commands while maintaining command-specific options.
---
This video is based on the question https://stackoverflow.com/q/63827020/ asked by the user 'edt_devel' ( https://stackoverflow.com/u/2328956/ ) and on the answer https://stackoverflow.com/a/63828155/ provided by the user 'Tryph' ( https://stackoverflow.com/u/2696355/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to mix shared and exclusive arguments in argparse

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Mastering argparse: Mixing Shared and Exclusive Arguments

When building command-line applications in Python, the argparse module offers a flexible way to handle argument parsing. However, one common challenge developers face is mixing shared and exclusive arguments across various commands. In this guide, we’ll address a common issue you may encounter when trying to implement commands with shared arguments while keeping some unique to each command.

The Problem

Imagine you have a command-line tool where specific commands share a few options, yet each command also has its unique set of options. For example, you might have two commands, cmd1 and cmd2, both needing to accept two common options but also requiring separate options unique to each command.

Here's a simplified version of what's usually attempted using argparse:

[[See Video to Reveal this Text or Code Snippet]]

This approach often leads to trouble as the main parser can intercept commands preventing the subparsers from working correctly.

Identifying the Mistake

Consider the following error message you might encounter:

[[See Video to Reveal this Text or Code Snippet]]

This occurs because the primary parser intercepts the 'command' argument, leading to an inability to parse the subcommands. The first command (cmd1) might run correctly, while the second (cmd2) fails.

Solution Breakdown

Let’s break down a proper solution into manageable steps:

1. Remove the Main Command Interception

Simply removing the line parser.add_argument('command', help='Subcommand to run') allows the command names cmd1 and cmd2 to be parsed correctly by their corresponding subparsers. Here's how it works:

[[See Video to Reveal this Text or Code Snippet]]

2. Using a Custom Subcommand Parser

To keep parts of the argument structure organized and shared between commands, you can define a subclass of argparse.ArgumentParser. This subclass will include the shared arguments:

[[See Video to Reveal this Text or Code Snippet]]

Now, when creating subparsers, you can specify that this custom parser should be used for all subcommands:

[[See Video to Reveal this Text or Code Snippet]]

3. Putting it All Together

After implementing the changes, your command-line tool should look like this:

[[See Video to Reveal this Text or Code Snippet]]

Example Execution

After refactoring, running the tool should yield the following results:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Utilizing shared and exclusive arguments in argparse need not be a headache. By eliminating intercepting command inputs, defining a custom argument parser, and managing subcommands effectively, you can create powerful command-line applications.

With these insights in hand, you're ready to take full advantage of argparse in your projects. Happy coding!