script-sprawl-guard

To prevent Python script sprawl, enforce canonical invocation patterns that prohibit creating unnecessary wrapper scripts, ensuring a clean and maintainable codebase by running modules directly via standard command line methods.

The best way to run a Python module without a new script is to use canonical invocation methods like `python file.py` or `python -m module`, following a strict decision tree for entrypoint selection to maintain codebase maintainability.

You need to use `python -m module` instead of a wrapper executable when invoking Python utilities to comply with canonical invocation policies, which prevents the uncontrolled proliferation of new runner script files.

To determine the correct entrypoint for a Python utility, consult an entrypoint decision tree that provides a step-by-step process for selecting the sanctioned canonical invocation method over creating unnecessary wrapper executables.

Creating new runner scripts reduces Python code maintainability because it causes script sprawl, fragmenting execution patterns and cluttering the codebase with unmanaged wrapper files instead of relying on canonical invocation.

Using a wrapper executable for Python code is prohibited by canonical invocation policies, which mandate using sanctioned methods like `python file.py` to prevent script sprawl and ensure maintainable code execution.