Python Separate CLI Parsing from Application Logic

Keep CLI parsing independent of the calculation it triggers.

What It Does and Why It Matters

When parse_args() is buried inside domain functions, calling those functions from tests or other modules becomes awkward. Make a pure function that receives ordinary values, and have a small main() function translate CLI arguments into those values. This design also separates validation of arguments from the program’s central algorithm.

With argv=None, parse_args() uses real command-line arguments; passing a list supports deterministic examples and tests.

Step-by-Step Example

Start with the complete example below. Read the inputs and predict what the final print statement will show before you run it.

import argparse
def rectangle_area(width, height):
    if width < 0 or height < 0:
        raise ValueError("Dimensions must be nonnegative")
    return width * height
def main(argv=None):
    parser = argparse.ArgumentParser()
    parser.add_argument("width", type=float)
    parser.add_argument("height", type=float)
    args = parser.parse_args(argv)
    return rectangle_area(args.width, args.height)
print(main(["3", "4"]))

How the Code Works

The imports make these standard-library tools available: argparse.
The definition of rectangle_area, main creates reusable behavior; its body runs only when called or instantiated as appropriate.
The print calls display the results. Compare these results with the method’s documented return type and the input used.

Expected output:

12.0

For the demonstrated inputs, Python displays '12.0'. This result follows from the operation described above; change one input at a time to understand which rule matters.

What to Notice

Pay attention to the accepted input types, the returned value and the boundary behavior. Predict what changes if you replace the example input with an empty, zero, negative or missing value, where that value is meaningful for this operation.

If the task uses a library function, inspect its documented exceptions and return type before reusing it inside a larger function.

Where You Would Use This

This is useful for scripts, maintenance commands and automated workflows. Treat inputs as untrusted, keep normal results separate from errors, and choose exit codes consistently. Keep reusable logic outside the command-line parser so it can be tested independently.

Practice Exercise

Write three ordinary tests for rectangle_area() without invoking argparse.

Before running your edited example, write down the result you expect. Then test at least one valid boundary or deliberately invalid value, using appropriate exception handling where necessary.

Reference: official Python documentation for the complete API contract and version notes.

Common Beginner Mistakes

Accessing global sys.argv directly inside a reusable calculation function.
Treating successful output as proof of a successful exit code, or accepting an unchecked path or command argument.

Key Takeaways

Keep CLI parsing independent of the calculation it triggers.
When parse_args() is buried inside domain functions, calling those functions from tests or other modules becomes awkward.
Write three ordinary tests for rectangle_area() without invoking argparse.