ddargparse - dataclass driven argparse
A small Python library that simplifies command-line argument parsing by leveraging dataclasses. It allows developers to define their command-line interfaces using dataclass fields, making the code more concise and easier to maintain. With ddargparse, you can easily create complex command-line applications with minimal boilerplate code. It puts a particular focus on properly handling type annotations and defaults, minimizing additional required annotation and maintaining interoperability with the standard argparse.
Installation
pip install ddargparse
Usage
Mode a: argparse + dataclasses
Subclass OptionsBase and annotate fields with standard argparse metadata via the dataclasses.field function (help, required, positional, metavar). Then call register_cli_args to populate an ArgumentParser and from_cli_args to instantiate your options from the parsed result.
Step 1: Option dataclass definition
from argparse import ArgumentParser
from dataclasses import dataclass, field
import ddargparse
@dataclass
class Options(ddargparse.OptionsBase):
inputfile: str = field(
metadata={"help": "Input file", "positional": True, "metavar": "FILE"},
)
verbose: bool = field(
metadata={"help": "Enable verbose output"},
)
tags: list[str] = field(
default_factory=list,
metadata={"help": "One or more tags"},
)
@dataclass
class DoSomethingOptions(ddargparse.OptionsBase):
threshold: str = field(metadata={"help": "Some threshold"})
mode: SomeMode = field(default=SomeMode.DEFAULT, metadata={"help": "Mode to be used"})
Step 2: CLI argument parser declaration
parser = ArgumentParser()
# register dataclass options as argparse parser arguments
Options.register_cli_args(parser)
subparsers = parser.add_subparsers(dest="subcommand")
subparser = subparsers.add_parser("do-something")
# register dataclass options as argparse subparser arguments
DoSomethingOptions.register_cli_args(subparser)
Step 3: CLI argument parsing and option dataclass instantiation
args = parser.parse_args()
# obtain instance of dataclass with global options
options = Options.from_parsed_cli_args(args)
match args.subcommand:
case "do-something":
# obtain instance of dataclass with subcommand options
do_something_options = DoSomethingOptions.from_parsed_cli_args(args)
Mode b: dataclass only
In this mode, control over argparse is handed over to ddargparse entirely and happening under the hood. The advantage is that subcommands can be expressed implicitly in the dataclass hierarchy.
Step 1: Option and subcommand dataclass definition
from argparse import ArgumentParser
from dataclasses import dataclass, field
import ddargparse
@dataclass
class Options(ddargparse.OptionsBase):
"The docstring is used as description in the CLI interface"
inputfile: str = field(
metadata={"help": "Input file", "positional": True, "metavar": "FILE"},
)
verbose: bool = field(
metadata={"help": "Enable verbose output"},
)
tags: list[str] = field(
default_factory=list,
metadata={"help": "One or more tags"},
)
subcommand_do_something: DoSomethingOptions | None
class SomeMode(Enum):
DEFAULT = 0
FAST = 1
@dataclass
class DoSomethingOptions(ddargparse.OptionsBase):
"""This is the subcommand description
The first line of the subcommand is used as short help, while the full description
is displayed upon "mytool do-something --help"
"""
threshold: str = field(metadata={"help": "Some threshold"})
mode: SomeMode = field(default=SomeMode.DEFAULT, metadata={"help": "Mode to be used"})
Step 2: CLI argument parsing and option dataclass instantiation
Then, the entire hierarchy of options, including automatic determination of the
selected subcommand and its options can be obtained via calling parse_argv() on the
top-level Options class.
options = Options.from_cli_args()
Features
- Declare CLI arguments as typed dataclass fields — no repetitive
add_argumentcalls, no need for thetypeargument. Automatic convertion of field names into kebab-case CLI arguments. - Booleans (
store_true/store_false), and list arguments (nargs="+") are inferred automatically from the dataclass field definitions. - Custom parse methods: define a
parse_<field_name>(cls, value: str)classmethod to override the argument type converter. - Mark options as positional (
"positional": True). - Automatic and natural inference whether option is required (no
field(default=...)and no| Nonein type annotation). - Choose between append-style (
--arg item1 --arg item2 --arg item3) and nargs-style (default,--arg item1 item2 item3) list arguments viaregister_cli_args(..., list_append=True|False)orparse_argv(list_append=True|False). - Proper support for enums: simply specify an enum type and ddargparse handles ensures that proper (lower, kebab-cased) choices are inferred from the enum item names and the correct type is returned.
- Seamless integration with standard argparse API or dataclass only modes that hides all technical details of the argument parsing.
- No additional dependencies.
Requirements
- Python ≥ 3.11
License
See LICENSE.
Metadata
Release files for ddargparse 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ddargparse-1.0.1.tar.gz | 12.0 kB | With provenance | Details for ddargparse-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ddargparse-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for ddargparse-1.0.1-py3-none-any.whl |
Total release size: 21.4 kB
Release files / ddargparse-1.0.1.tar.gz
| Download URL | ddargparse-1.0.1.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3055f45de16c7f87596226da55d887b8294d28bede0e4ffb254fec1b00555592
|
|
BLAKE2b-256 checksum How to use checksums |
5dd304af5b7fe4e9f8d4cc88f475eab44ab440f48e9db5c1d137dedb51b9e8df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / ddargparse-1.0.1-py3-none-any.whl
| Download URL | ddargparse-1.0.1-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1623adc4467f7e5455407cd487fb94027140f84a439d8cadbdedef86189d87d4
|
|
BLAKE2b-256 checksum How to use checksums |
0b8ec1a7bf020c6402a8840a529d8d2db129f76ecffbe4469f1ab1f54f4a6c03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logSecurity for ddargparse 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ddargparse-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.