Skip to content

helmut-hoffer-von-ankershoffen/oe-python-template

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🧠 OE Python Template

License PyPI - Python Version CI Read the Docs Quality Gate Security Maintainability Technical Debt Code Smells CodeQL Dependabot Renovate enabled Coverage Ruff MyPy GitHub - Version GitHub - Commits PyPI - Version PyPI - Status Docker - Version Docker - Size Copier Open in Dev Containers Open in GitHub Codespaces Vercel Deploy Better Stack Uptime

Tip

📚 Online documentation - 📖 PDF Manual


Copier template to scaffold Python projects compliant with best practices and modern tooling.

Scaffolding

This Copier template enables you to quickly generate (scaffold) a Python package with fully functioning build and test automation:

  1. Projects generated from this template can be easily updated to benefit from improvements and new features of the template.
  2. During project generation, you can flexibly configure naming of the Python distribution, import package, main author, GitHub repository, organization, and many other aspects to match your specific requirements (see copier.yml for all available options).

Development Infrastructure

Projects generated with this template come with a comprehensive development toolchain and quality assurance framework that supports the entire software development lifecycle - from coding and testing to documentation, release management, and compliance auditing. This infrastructure automates routine tasks, enforces code quality standards, and streamlines the path to production:

  1. Linting with Ruff
  2. Static type checking with mypy
  3. Complete set of pre-commit hooks including detect-secrets and pygrep
  4. Unit and E2E testing with pytest including parallel test execution
  5. Matrix testing in multiple environments with nox
  6. Test coverage reported with Codecov and published as release artifact
  7. CI/CD pipeline automated with GitHub Actions with parallel and reusable workflows, including scheduled testing, release automation, and multiple reporting channels and formats
  8. CI/CD pipeline can be run locally with act
  9. Code quality and security checks with SonarQube and GitHub CodeQL
  10. Dependency monitoring and vulnerability scanning with pip-audit, trivy, Renovate, and GitHub Dependabot
  11. Error monitoring and profiling with Sentry (optional)
  12. Logging and metrics with Logfire (optional)
  13. Prepared for uptime monitoring and scheduled tests with betterstack or alternatives
  14. Licenses of dependencies extracted with pip-licenses, matched with allow list, and published as release artifacts in CSV and JSON format for further compliance checks
  15. Generation of attributions from extracted licenses
  16. Software Bill of Materials (SBOM) generated in CycloneDX and SPDX formats with cyclonedx-python resp. trivy, published as release artifacts
  17. Version and release management with bump-my-version
  18. Changelog and release notes generated with git-cliff
  19. Documentation generated with Sphinx including reference documentation for the library, CLI, and API
  20. Documentation published to Read The Docs including generation of PDF and single page HTML versions
  21. Documentation including dynamic badges, setup instructions, contribution guide and security policy
  22. Interactive OpenAPI specification with Swagger
  23. Python package published to PyPI
  24. Multi-stage build of fat (all extras) and slim (no extras) multi-arch (arm64 and amd64) Docker images, running non-root within immutable container
  25. Docker images published to Docker.io and GitHub Container Registry with artifact attestations
  26. One-click development environments with Dev Containers and GitHub Codespaces
  27. Settings for use with VSCode
  28. Settings and custom instructions for use with GitHub Copilot
  29. API deployed as serverless function to Vercel (optional)

Multi-head Application Features

Beyond development tooling, projects generated with this template include the code, documentation, and configuration of a fully functioning service and multi-head application. This reference implementation serves as a starting point for your own business logic with modern patterns and enterprise practices already in place:

  1. Usable as library with "Hello" module exposing a simple service that can say "Hello, world!" and echo utterances.
  2. Comfortable command-line interface (CLI) with Typer
  3. Versioned webservice API with FastAPI
  4. Cross-platform Graphical User Interface (GUI) with NiceGUI running in a browser or native window
  5. Interactive Jupyter notebook and reactive Marimo notebook
  6. Simple Web UI with Streamlit
  7. Modular architecture auto-discovers and registers services, CLI commands, API routes and GUI pages exposed by domain modules
  8. Validation and settings management with pydantic
  9. System module providing aggregate health and info to the runtime, compiled settings, and further info provided by domain modules
  10. Health and Info available via command, webservice API (info passsword protected) and GUI
  11. Flexible logging and instrumentation, including support for Sentry and Logfire
  12. Hello service demonstrates use of custom real time metrics collected via Logfire
  13. Configuration to run the CLI and API in a Docker container including setup for Docker Compose

Explore here for what's generated out of the box. While this template comes with multiple application interfaces ("heads") - Library, CLI, API, GUI, notebooks, and Streamlit; running native and within Docker - they're included to demonstrate capabilities and provide implementation patterns. You're expected to use this as a foundation, keeping only the interfaces relevant to your project's requirements. The modular architecture makes it easy to:

  1. Remove unnecessary interfaces to simplify your codebase
  2. Adapt existing interfaces to your specific use cases
  3. Focus on your core business logic without reimplementing infrastructure
  4. Add new interfaces while leveraging the existing patterns

Generate a new project

To generate, build and release a fully functioning project in a few minutes, follow these 5 steps:

Step 1: Execute the following command to install or update tooling.

# Install Homebrew, uv package manager, copier and further dev tools
curl -LsSf https://raw.githubusercontent.com/helmut-hoffer-von-ankershoffen/oe-python-template/HEAD/install.sh | sh

Step 2: Create a repository on GitHub, clone to your local machine, and change into it's directory.

Step 3: Execute the following command to generate a new project based on this template.

# Ensure to stand in your freshly created git repository before executing this command
copier copy --trust gh:helmut-hoffer-von-ankershoffen/oe-python-template .

Step 4: Execute the following commands to push your initial commit to GitHub.

git add .
git commit -m "chore: Initial commit"
git push

Check the Actions tab of your GitHub repository: The CI/CD workflow of your project is already running!

The workflow will fail at the SonarQube step, as this external service is not yet configured for our new repository. We will configure SonarQube and other services in the next step!

Notes:

  1. Check out this manual on how to set up signed commits

Step 5: Follow the instructions to wire up external services such as CloudCov, SonarQube Cloud, Read The Docs, Docker.io, and Streamlit Community Cloud.

Step 6: Release the first version of your project

make bump

Notes:

  1. You can remove the above sections - from "Scaffolding" to this notes - post having successfully generated your project.
  2. The following sections refer to the dummy application and service generated into the tests and src folder by this template. Use the documentation and code as inspiration, adapt to your business logic, or remove and start documenting and coding from scratch.

Overview

Adding OE Python Template to your project as a dependency is easy. See below for usage examples.

uv add oe-python-template             # add dependency to your project

If you don't have uv installed follow these instructions. If you still prefer pip over the modern and fast package manager uv, you can install the library like this:

pip install oe-python-template        # add dependency to your project

Executing the command line interface (CLI) in an isolated Python environment is just as easy:

uvx oe-python-template hello world               # prints "Hello, world! [..]"
uvx oe-python-template hello echo "Lorem Ipsum"  # echos "Lorem Ipsum"
uvx oe-python-template gui                       # opens the graphical user interface (GUI)
uvx --with "oe-python-template[examples]" oe-python-template gui  # opens the graphical user interface (GUI) with support for scientific computing
uvx oe-python-template system serve              # serves web API
uvx oe-python-template system serve --port=4711  # serves web API on port 4711
uvx oe-python-template system openapi            # serves web API on port 4711

Notes:

  1. The API is versioned, mounted at /api/v1 resp. /api/v2
  2. While serving the web API go to http://127.0.0.1:8000/api/v1/hello-world to see the respons of the hello-world operation.
  3. Interactive documentation is provided at http://127.0.0.1:8000/api/docs

The CLI provides extensive help:

uvx oe-python-template --help                # all CLI commands
uvx oe-python-template hello world --help    # help for specific command
uvx oe-python-template hello echo --help
uvx oe-python-template gui --help
uvx oe-python-template system serve --help
uvx oe-python-template system openapi --help

Operational Excellence

This project is designed with operational excellence in mind, using modern Python tooling and practices. It includes:

  1. Various examples demonstrating usage: a. Simple Python script b. Streamlit web application deployed on Streamlit Community Cloud c. Jupyter and Marimo notebook
  2. Complete reference documentation for the library, for the CLI and for the API on Read the Docs
  3. Transparent test coverage including unit and E2E tests (reported on Codecov)
  4. Matrix tested with multiple python versions to ensure compatibility (powered by Nox)
  5. Compliant with modern linting and formatting standards (powered by Ruff)
  6. Up-to-date dependencies (monitored by Renovate and Dependabot)
  7. A-grade code quality in security, maintainability, and reliability with low technical debt and codesmell (verified by SonarQube)
  8. Additional code security checks using CodeQL
  9. Security Policy
  10. License compliant with the Open Source Initiative (OSI)
  11. 1-liner for installation and execution of command line interface (CLI) via uv(x) or Docker
  12. Setup for developing inside a devcontainer included (supports VSCode and GitHub Codespaces)

Usage Examples

The following examples run from source - clone this repository using git clone git@github.com:helmut-hoffer-von-ankershoffen/oe-python-template.git.

Minimal Python Script:

"""Example script demonstrating the usage of the service provided by OE Python Template."""

from rich.console import Console

from oe_python_template.hello import Service

console = Console()

message = Service.get_hello_world()
console.print(f"[blue]{message}[/blue]")

Show script code - Read the reference documentation

Streamlit App

Serve the functionality provided by OE Python Template in the web by easily integrating the service into a Streamlit application.

Try it out! - Show the code

... or serve the app locally

uv sync --all-extras                                # Install streamlit dependency part of the examples extra, see pyproject.toml
uv run streamlit run examples/streamlit.py          # Serve on localhost:8501, opens browser

Vercel Serverless Function

Serve the API as a serverless function on Vercel

Notebooks

Jupyter

Show the Jupyter code

... or run within VSCode

uv sync --all-extras                                # Install dependencies required for examples such as Juypyter kernel, see pyproject.toml

Install the Jupyter extension for VSCode

Click on examples/notebook.ipynb in VSCode and run it.

Marimo

Show the marimo code

Execute the notebook as a WASM based web app

uv sync --all-extras                                # Install ipykernel dependency part of the examples extra, see pyproject.toml
uv run marimo run examples/notebook.py --watch      # Serve on localhost:2718, opens browser

or edit interactively in your browser

uv sync --all-extras                                # Install ipykernel dependency part of the examples extra, see pyproject.toml
uv run marimo edit examples/notebook.py --watch     # Edit on localhost:2718, opens browser

... or edit interactively within VSCode

Install the Marimo extension for VSCode

Click on examples/notebook.py in VSCode and click on the caret next to the Run icon above the code (looks like a pencil) > "Start in marimo editor" (edit).

... or without prior cloning of the repository

uvx marimo run https://raw.githubusercontent.com/helmut-hoffer-von-ankershoffen/oe-python-template/refs/heads/main/examples/notebook.py

Command Line Interface (CLI)

Run with uvx

Show available commands:

uvx oe-python-template --help

Execute commands:

uvx oe-python-template hello world
uvx oe-python-template hello echo --help
uvx oe-python-template hello echo "Lorem"
uvx oe-python-template hello echo "Lorem" --json
uvx oe-python-template gui
uvx --with "oe-python-template[examples]" oe-python-template gui  # opens the graphical user interface (GUI) with support for scientific computing
uvx oe-python-template system info
uvx oe-python-template system health
uvx oe-python-template system openapi
uvx oe-python-template system openapi --output-format=json
uvx oe-python-template system serve

See the reference documentation of the CLI for detailed documentation of all CLI commands and options.

Environment

The service loads environment variables including support for .env files.

cp .env.example .env              # copy example file
echo "THE_VAR=MY_VALUE" > .env    # overwrite with your values

Now run the usage examples again.

Run with Docker

You can as well run the CLI within Docker.

docker run helmuthva/oe-python-template --help
docker run helmuthva/oe-python-template hello world
docker run helmuthva/oe-python-template hello echo --help
docker run helmuthva/oe-python-template hello echo "Lorem"
docker run helmuthva/oe-python-template hello echo "Lorem" --json
docker run helmuthva/oe-python-template system info
docker run helmuthva/oe-python-template system health
docker run helmuthva/oe-python-template system openapi
docker run helmuthva/oe-python-template system openapi --output-format=json
docker run helmuthva/oe-python-template system serve

The default Docker image includes all extras. Additionally a slim image is provided, with no extras. Run as follows

docker run helmuthva/oe-python-template-slim --help
docker run helmuthva/oe-python-template-slim hello world

You can pass environment variables as parameters:

docker run --env OE_PYTHON_TEMPLATE_HELLO_LANGUAGE=de_DE helmuthva/oe-python-template hello world
docker run --env OE_PYTHON_TEMPLATE_HELLO_LANGUAGE=en_US helmuthva/oe-python-template hello world

A docker compose stack is provided. Clone this repository using git clone git@github.com:helmut-hoffer-von-ankershoffen/oe-python-template.git and enter the repository folder.

The .env is passed through from the host to the Docker container.

docker compose run --remove-orphans oe-python-template --help
docker compose run --remove-orphans oe-python-template hello world
docker compose run --remove-orphans oe-python-template hello echo --help
docker compose run --remove-orphans oe-python-template hello echo "Lorem"
docker compose run --remove-orphans oe-python-template hello echo "Lorem" --json
docker compose run --remove-orphans oe-python-template system info
docker compose run --remove-orphans oe-python-template system health
docker compose run --remove-orphans oe-python-template system openapi
docker compose run --remove-orphans oe-python-template system openapi --output-format=json
echo "Running OE Python Template's API container as a daemon ..."
docker compose up -d
echo "Waiting for the API server to start ..."
sleep 5
echo "Checking health of v1 API ..."
curl http://127.0.0.1:8000/api/v1/healthz
echo ""
echo "Saying hello world with v1 API ..."
curl http://127.0.0.1:8000/api/v1/hello/world
echo ""
echo "Swagger docs of v1 API ..."
curl http://127.0.0.1:8000/api/v1/docs
echo ""
echo "Checking health of v2 API ..."
curl http://127.0.0.1:8000/api/v2/healthz
echo ""
echo "Saying hello world with v1 API ..."
curl http://127.0.0.1:8000/api/v2/hello/world
echo ""
echo "Swagger docs of v2 API ..."
curl http://127.0.0.1:8000/api/v2/docs
echo ""
echo "Shutting down the API container ..."
docker compose down

Extra: Lorem Ipsum

Dolor sit amet, consectetur adipiscing elit. Donec a diam lectus. Sed sit amet ipsum mauris. Maecenas congue ligula ac quam.

Further Reading

  • Inspect our security policy with detailed documentation of checks, tools and principles.
  • Check out the CLI reference with detailed documentation of all CLI commands and options.
  • Check out the library reference with detailed documentation of public classes and functions.
  • Check out the API reference with detailed documentation of all API operations and parameters.
  • Our release notes provide a complete log of recent improvements and changes.
  • In case you want to help us improve 🧠 OE Python Template: The contribution guidelines explain how to setup your development environment and create pull requests.
  • We gratefully acknowledge the open source projects that this project builds upon. Thank you to all these wonderful contributors!

Star History

Star History Chart