Files
astrape-oracle/pyproject.toml
T
rpotter6298 9a4ee8e0cf Flatten to a single package directory
The checkout is now astrape/astrape-oracle, not astrape/astrape-oracle/<package>. The package
contents move to the repository root and pyproject maps the package name to
'.' via package-dir, with the subpackages listed explicitly.

The systemd units move out to /srv/astrape/deploy/systemd, outside every
repository, because they describe this deployment rather than any one
component.

Verified both install modes: editable, which is how the deployment runs, and
a plain wheel install, which is what the container build does.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-30 15:05:17 +02:00

18 lines
834 B
TOML

[build-system]
requires = ["setuptools>=68"]
build-backend = "setuptools.build_meta"
[project]
name = "astrape-oracle"
version = "0.1.0"
description = "Forecasting runtime: weather ingest, oracle snapshots, TCN training"
requires-python = ">=3.12"
dependencies = ["gibil", "astrape-ems", "psycopg[binary]>=3.2,<4"]
# Flat layout: this repository *is* the package. package-dir maps astrape_oracle to the
# repository root rather than to a nested astrape_oracle/ directory, so the checkout is
# astrape/astrape-oracle and not astrape/astrape-oracle/astrape_oracle.
[tool.setuptools]
packages = ["astrape_oracle", "astrape_oracle.classes", "astrape_oracle.classes.weather", "astrape_oracle.scripts", "astrape_oracle.scripts.daemons", "astrape_oracle.scripts.debug", "astrape_oracle.scripts.tcn"]
package-dir = {"astrape_oracle" = "."}