pyproject.toml

[project]
name = "screening"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.14"
dependencies = [
    "azure-data-tables>=12.7.0",
    "azure-identity>=1.25.3",
    "azure-storage-queue>=12.17.0",
    "en-core-web-sm",
    "fastapi[standard]>=0.139.2",
    "instructor>=1.15.4",
    "openai>=2.47.0",
    "pip>=26.1.2",
    "presidio-analyzer>=2.2.364",
    "presidio-anonymizer>=2.2.364",
    "protobuf>=7.35.1",
    "pydantic-settings>=2.14.2",
    "sentencepiece>=0.2.2",
    "torch>=2.13.0",
    "transformers>=5.14.1",
]

[tool.uv.sources]
en-core-web-sm = { url = "https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.8.0/en_core_web_sm-3.8.0-py3-none-any.whl" }

[dependency-groups]
dev = [
    "pytest>=9.1.1",
    "pytest-asyncio>=1.4.0",
    "tdd-guard-pytest>=0.1.2",
    "ty>=0.0.63",
    {include-group = "evals"},
]
# Only `evals/` imports deepeval -- the LLM adapter carries no eval
# instrumentation. A separate named group (rather than listing it flatly
# under `dev`) keeps `uv sync --no-dev` (what the Dockerfile runs) from
# pulling deepeval into the production image. Note: this does NOT make
# `evals/` runnable standalone via `--only-group evals` -- every eval script
# here is a pytest test module, so `pytest` (in `dev`) is still required
# regardless of which group installed `deepeval`.
evals = [
    "deepeval>=4.1.5",
]

[tool.pytest.ini_options]
pythonpath = ["."]
markers = [
    "live: hits real models / network (slow)",
    "prod: hits the deployed prod endpoint",
    "quality: hits a live LLM plus a judge LLM for output-quality evals (costs tokens)"
]
tdd_guard_project_root = "."

[tool.fastapi]
entrypoint = "app.api.main:app"