SAService Architect Back to designer
SAService ArchitectDocumentation
Code generation workspace -> pyproject packages

Python project

Python generation creates independently buildable service and Module packages joined by root uv-based automation.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

Behavior

  • The root pyproject.toml and uv.lock pin the generated Python workspace.
  • Each service uses a src layout whose package name is derived from Service.name.
  • src/<service-package>/main.py starts the service.
  • src/<service-package>/internal/app contains generated graph assembly, while internal/functions contains preserved business implementations.
  • Referenced user-defined Modules become independent Python packages containing only the public types, functions, OpenAPI, or protobuf artifacts selected by graph references.

Python service directories

Important paths in each generated Python service.

PathOwnershipDescription
pyproject.tomlManaged

Package metadata, dependencies, tools, and service entrypoint.

src/<service-package>/main.pyGenerated entrypoint

Starts configuration and the ServiceLib runtime.

src/<service-package>/internal/app/Generated

Runtime graph, connector, endpoint, and lifecycle assembly.

src/<service-package>/internal/functions/Preserved

Business operators and endpoint handlers.

src/<service-package>/internal/config/Mixed

Generated typed configuration and custom extensions.

src/<service-package>/models/Mixed

Service-local model and serde code.

tests/Preserved + support

Business tests and generated test support.

Dockerfile + Dockerfile.localManaged

Standalone runtime and development images.

Python service tree

<service-name>/
  pyproject.toml
  src/<service-package>/main.py
  src/<service-package>/internal/app/
  src/<service-package>/internal/functions/
  src/<service-package>/internal/config/
  src/<service-package>/models/
  tests/ + config/ + graph/ + docs/
  grafana/ + helm/