A lightweight collection of small, single-file Python utilities and experiments. Each script is self-contained and focuses on doing one thing well.
- Requirements: Python 3.9+ (3.11 recommended)
- Optional: Create a virtual environment if a script has dependencies
python3 -m venv .venv
source .venv/bin/activate
pip install -U pip- Most scripts can be run directly with Python:
python3 path/to/script.pyorpython3 script_name
- If a script has a shebang (
#!/usr/bin/env python3) and executable bit, you can run it directly:./script_name
- Many scripts support
-h/--helpfor usage:python3 script_name -h
- If a script uses third‑party packages, it will mention them in its header/docstring.
- Install per-script requirements as needed, for example:
pip install requests rich(example)
- Single-file scripts live at the repo root (or a subfolder if they grow).
- Prefer:
- A short module docstring explaining purpose, inputs/outputs, and examples
argparsefor CLI flags and-h/--help- Clear exit codes and explicit error messages
- No secrets in code—use environment variables where necessary
- Create a new file with a descriptive name (e.g.,
foo_bar_tool.pyorfoo_bar_tool). - Include a docstring with:
- What it does
- How to run it
- Inputs/outputs (files, env vars)
- Use
argparseif it has parameters. - Document any dependencies in the docstring and keep them minimal.
- Test locally and add example commands to the docstring.
- Root contains individual scripts and this README.
- Temporary outputs or data files should be git‑ignored locally if large or generated.
- Use
python -m pip install -r requirements.txtif a script provides one. - Use
rufforblackif you prefer auto-formatting (optional). - On macOS:
python3refers to the system or Homebrew Python; prefer virtualenvs per script that needs packages.
No license specified yet. Add one if sharing publicly (e.g., MIT/Apache-2.0).