PyArgWriter is a Python module that simplifies the generation of ArgumentParser setups for Python classes and their methods. It provides a convenient way to define and manage command-line arguments for your Python applications.
You can install PyArgWriter using pip
:
pip install pyargwriter
Alternative from source code:
In root folder with pip:
pip install .
or with poetry:
poetry install
PyArgWriter offers the following command-line commands:
parse-code
: Parse given files and create YAML structure with structural parser information.write-code
: Read given parser YAML structure and create argument parser Python code.generate-argparser
: Generateparser.py
, which contains asetup_parser
function to set up an appropriate parser.
For more detailed information on available command-line arguments and usage examples, refer to the official documentation.
PyArgWriter depends strongly on information stated in the docstring. Your docstring should have a minimal structure like:
def add(a: int, b: int) -> int:
"""_summary_
Args:
a (int): _description_
b (int): _description_
Returns:
int: _description_
"""
return a + b
Usage PyArgWriter offers a command-line interface for generating and managing ArgumentParser setups. Below are the available commands and their usage:
python -m pyargwriter parse-code --input file1.py file2.py --output output.yaml [--log-level LOG_LEVEL]
Parse given Python files and create a YAML structure with structural parser information.
python -m pyargwriter write-code --input input.yaml [--output OUTPUT_DIR] [--pretty] [--log-level LOG_LEVEL]
Read a given parser YAML structure and generate argument parser Python code.
python -m pyargwriter generate-argparser --input file1.py file2.py [--output OUTPUT_DIR] [--pretty] [--log-level LOG_LEVEL]
Generate a parser.py file that contains a setup_parser function to set up an appropriate ArgumentParser. Common Options --log-level LOG_LEVEL: Sets the log level for command execution (default is "WARN"). --pretty (-p): If set, the generated code will be formatted with Black. For more detailed information on each command and additional options, run:
python -m pyargwriter <command> --help
In the function of the process class you want to create the argument parser, following types of an argument are supported:
- int
- float
- str
- bool flags
- list[int]
- List[int] # from typing
- list[float]
- List[float] # from typing
- list[str]
- List[str] # from typing
- list[bool]
- List[bool] # from typing
python -m pyargwriter generate-argparser --input examples/shopping.py examples/car.py --output examples --pretty
As an additional feature we support to combine your existing ArgumentParser
with the Hydra framework. All you need to do is to use a decorator we provide with our framework. A short example can be viewed below.
from omegaconf import DictConfig
from pyargwriter.decorator import add_hydra
class Entrypoint:
"""ML training pipeline"""
def __init__(self):
"""initiate pipeline"""
pass
@add_hydra("config", version_base=None)
def train(config: DictConfig, device: str):
"""start training process
Args:
config (DictConfig): container which contains
device (str): where to train on
"""
The decorator is indeed callable. Additionally to the usual hydra-arguments you have to pass in the config_var_name
which specifies which argument in the train
signature is the config object. After calling the pyargwriter tool you are now ready to go with a CLI which can now handle also almost all Hydra commands. Except the normal help
message you get from Hydra. For further interest in this message please refer to their website
The complete documentation for PyArgWriter, including detailed usage instructions and examples, can be found in the official documentation or at the documentation website.
Further you can have a look into the test coverage.
This project is licensed under the Apache 2.0 License - see the LICENSE file for details.
If you would like to contribute to PyArgWriter, please read our Contributing Guidelines for details on how to get started.
For any questions, issues, or feedback, please open an issue on our GitHub repository.
Here are some potential names for your tool, focusing on its functionality and the concept of automatically generating CLI interfaces:
- AutoCLI
- ClassCLI
- MethodCLI
- CLIBuilder
- ArgParserGen
- ClassParser
- Method2CLI
- CLIForge
- CLImate (a nod to "CLI" and "automate")
- CLIonize (like ionizing a class into a CLI)
- CLIckIt (emphasizing ease and speed)
- Parse-o-Matic
- Argonaut (exploring arguments and generating interfaces)
- CommandCrafter
- InterfaceSmith
- AutoArg
- PyCLI
- CodeCommander
- Argitect (argument architect)
- CommandWeaver
- ParseMaster
- CLIMaker
- MethodBridge
Each of these names is tailored to different branding styles. Do you have preferences about whether the name should be more functional, playful, or tech-inspired?
If you want the name to be short, easy to type, and terminal-friendly, here are some concise options:
- cli-gen
- argen (short for "argument generator")
- clify
- m2cli (short for "method to CLI")
- pycli
- cligen
- argcli
- cly (a super-short take on "CLI")
- cmdgen
- methcli (short for "method CLI") 11 . clipy
These names are minimal, straightforward, and easy to remember for developers. Let me know if any of these stand out!