@@ -1813,17 +1813,17 @@ Subcommands
18131813
18141814 The help argument provides a short description for this subcommand.
18151815 If provided, it will be listed next to the command in the main
1816- parser’s help message (e.g., `PROG --help `).
1816+ parser’s help message (e.g., `` PROG --help ` `).
18171817
18181818 The aliases argument allows you to provide a sequence of strings
18191819 that can be used as alternative names for this subcommand
1820- (e.g., `aliases=['co'] ` for a `'checkout' ` command).
1820+ (e.g., `` aliases=['co'] `` for a `` 'checkout' ` ` command).
18211821
18221822 The deprecated argument allows you to mark the subcommand as
1823- deprecated. When a deprecated subcommand is used, :mod: argparse
1823+ deprecated. When a deprecated subcommand is used, :mod: ` argparse `
18241824 will emit a warning.
18251825
1826- This returned :class: !ArgumentParser object can be modified as usual.
1826+ This returned :class: ` !ArgumentParser` ` object can be modified as usual.
18271827
18281828 *Examples *
18291829
@@ -1844,6 +1844,7 @@ Subcommands
18441844 >>> parser.parse_args(['fly']) # doctest: +SKIP
18451845 chicken.py: warning: command 'fly' is deprecated
18461846 Namespace()
1847+
18471848 One particularly effective way of handling subcommands is to combine the use
18481849 of the :meth: `~ArgumentParser.add_subparsers ` method with calls to :meth: `~ArgumentParser.set_defaults ` so
18491850 that each subparser knows which Python function it should execute. For
0 commit comments