pyproject.toml

[project]
name = "omop-constructs"
dynamic = ["version"]
description = "For building complex constructs on top of the omop-alchemy library."
readme = "README.md"
authors = [
    { name = "Georgie Kennedy", email = "georgina.kennedy@unsw.edu.au" }
]
requires-python = ">=3.12"
dependencies = [
    "oa-configurator>=1.2.1,<2",
    "omop-alchemy[postgres]>=1.1,<2",
    "omop-semantics>=0.6.0",
    "orm-loader>=1.0,<2",
    "sqlalchemy>=2.0.45",
]

[project.optional-dependencies]
dev = [
    "ipython>=9.8.0",
    # <0.16 deliberately: ruff 0.16 widened its default rule set enormously
    # (omop-alchemy reports 0 findings on 0.15.14 and 607 on 0.16.3). Every
    # sibling is green only because its lockfile predates 0.16. Lifting this
    # bound is a stack-wide decision, not a per-repo one.
    "ruff>=0.15,<0.16",
    "ty==0.0.61",
    "pytest>=9.0.3",
    "pytest-cov>=7.0.0",
    "tornado>=6.5.5",
    "mkdocs<2.0",
    "mkdocs-material",
    "mkdocstrings[python]",
    "mkdocs-mermaid2-plugin",
    "mkdocs-table-reader-plugin",
    "mkdocs-macros-plugin",
    "pygments>=2.20.0"
]

[project.scripts]
omop-constructs = "omop_constructs.cli:main"

[project.entry-points."omop.config"]
omop_constructs = "omop_constructs.config:OmopConstructsConfig"

[build-system]
requires = ["hatchling", "hatch-vcs"]
build-backend = "hatchling.build"

[tool.hatch.version]
source = "vcs"
raw-options = { tag_regex = '^v?(?P<version>[0-9]+\.[0-9]+\.[0-9]+)$' }

[tool.hatch.build.targets.wheel]
packages = ["src/omop_constructs"]

[tool.uv]
cache-keys = [{ file = "pyproject.toml" }, { git = { commit = true, tags = true } }]

[tool.ruff.lint]
extend-select = ["B006", "PIE810"]

[tool.ty.rules]
# todo: these shouldn't remain here long term - for cicd initial deployment for now
invalid-argument-type = "ignore"
unused-type-ignore-comment = "ignore"
unresolved-attribute = "ignore"

[tool.pytest.ini_options]
testpaths = ["tests"]
markers = [
    "postgres: requires a configured PostgreSQL database via ENGINE_CDM or ENGINE",
]