transitmatters 0.1.0__tar.gz

transitmatters-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,49 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: docs-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+
+      - name: Install dev dependencies
+        run: uv sync --dev
+
+      - name: Build API docs
+        run: uv run python scripts/docs.py -o site
+
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    # Pull requests only check that the docs build.
+    if: github.ref == 'refs/heads/main'
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write # required to deploy to GitHub Pages
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

transitmatters-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,49 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v6
+
+      - name: Check tag matches version
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          version="$(uv version --short)"
+          if [ "$tag" != "$version" ]; then
+            echo "::error::Release tag $GITHUB_REF_NAME does not match pyproject version $version"
+            exit 1
+          fi
+
+      - name: Build
+        run: uv build
+
+      - name: Smoke test wheel
+        run: uv run --isolated --no-project --with dist/*.whl python -c "import transitmatters._generated"
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/transitmatters
+    permissions:
+      id-token: write # required for trusted publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - uses: pypa/gh-action-pypi-publish@release/v1

transitmatters-0.1.0/.github/workflows/sync-spec.yml

@@ -0,0 +1,76 @@
+name: Sync upstream OpenAPI spec
+
+on:
+  schedule:
+    - cron: "17 13 * * 1" # Mondays 13:17 UTC (~9am Boston)
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: "Upstream branch, tag, or SHA to sync to"
+        required: false
+        default: main
+
+permissions:
+  contents: write
+  pull-requests: write
+
+concurrency:
+  group: sync-spec
+  cancel-in-progress: true
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: astral-sh/setup-uv@v6
+        with:
+          enable-cache: true
+
+      - name: Install dev dependencies
+        run: uv sync --dev
+
+      - name: Fetch upstream spec
+        id: sync
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: uv run python scripts/sync_spec.py --ref "${{ inputs.ref || 'main' }}"
+
+      - name: Regenerate client
+        if: steps.sync.outputs.changed == 'true'
+        run: |
+          uv run openapi-python-client generate \
+            --path spec/openapi.json \
+            --config openapi-config.yml \
+            --meta none \
+            --output-path src/transitmatters/_generated \
+            --overwrite
+
+      - name: Run tests
+        if: steps.sync.outputs.changed == 'true'
+        continue-on-error: true # still open the PR; failures show up in its checks
+        run: uv run pytest -q
+
+      - name: Open pull request
+        if: steps.sync.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@v7
+        with:
+          branch: chore/sync-openapi-spec
+          delete-branch: true
+          commit-message: "chore: sync OpenAPI spec to upstream ${{ steps.sync.outputs.short_sha }}"
+          title: "Sync OpenAPI spec to upstream ${{ steps.sync.outputs.short_sha }}"
+          body: |
+            Automated sync of `server/openapi.json` from
+            [transitmatters/t-performance-dash@${{ steps.sync.outputs.short_sha }}](https://github.com/transitmatters/t-performance-dash/commit/${{ steps.sync.outputs.sha }}).
+
+            - `spec/openapi.json` updated
+            - `spec/UPSTREAM_SHA` bumped
+            - `src/transitmatters/_generated/` regenerated
+
+            Review the spec diff for new or changed endpoints, and update the
+            wrapper in `src/transitmatters/` if needed.
+          labels: dependencies
+          add-paths: |
+            spec/
+            src/transitmatters/_generated/

transitmatters-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Built API docs
+site/

transitmatters-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

transitmatters-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 TransitMatters
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

transitmatters-0.1.0/PKG-INFO

@@ -0,0 +1,178 @@
+Metadata-Version: 2.5
+Name: transitmatters
+Version: 0.1.0
+Summary: Official Python client for the TransitMatters Data Dashboard API
+Project-URL: Repository, https://github.com/transitmatters/transitmatters-py
+Project-URL: Upstream API, https://github.com/transitmatters/t-performance-dash
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Programming Language :: Python :: 3
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Requires-Dist: attrs>=23.1
+Requires-Dist: httpx>=0.27
+Requires-Dist: python-dateutil>=2.8
+Description-Content-Type: text/markdown
+
+# transitmatters-py
+
+<!-- The API docs include this file from here down. -->
+
+MBTA performance data from the [TransitMatters Data Dashboard](https://dashboard.transitmatters.org),
+as Python objects: travel times, headways, dwells, ridership, service levels,
+delays, speed restrictions, and alerts.
+
+```sh
+pip install transitmatters
+```
+
+```python
+from transitmatters import TransitMatters
+
+tm = TransitMatters()
+
+# Every southbound Red Line trip from Alewife to Braintree on March 4, 2025
+trips = tm.travel_times("2025-03-04", from_stop="70061", to_stop="70105")
+print(trips[0].dep_dt, trips[0].travel_time_sec)
+```
+
+Dates can be `datetime.date` objects or `"YYYY-MM-DD"` strings, and date ranges
+include both ends. Parameters that take IDs accept one string or a list.
+
+## Which method do I want?
+
+**What happened on one day.** Each item is a single event.
+
+| Question | Method | Each item is |
+| --- | --- | --- |
+| How long did trips between two stops take? | `TransitMatters.travel_times` | a trip |
+| How long between departures at a stop? | `TransitMatters.headways` | a departure |
+| How long did vehicles sit at a stop? | `TransitMatters.dwells` | a stop a vehicle made |
+| Which alerts were posted for a route? | `TransitMatters.historical_alerts` | an alert |
+| Where were speed restrictions on a line? | `TransitMatters.speed_restrictions` | a zone, in `.zones` |
+
+**Trends over a date range.** Each item summarizes one day, week, or month.
+
+| Question | Method | Each item is |
+| --- | --- | --- |
+| Travel-time statistics between two stops | `TransitMatters.aggregate_travel_times` | a day |
+| ...also broken down by time of day | `TransitMatters.aggregate_travel_times_v2` | a day, or a 30-minute slot |
+| Headway statistics, bunching, and on-time counts at a stop | `TransitMatters.aggregate_headways` | a day |
+| Dwell-time statistics at a stop | `TransitMatters.aggregate_dwells` | a day |
+| Trip count, speed, and miles for a rapid transit line | `TransitMatters.trip_metrics` | a day, week, or month |
+| Minutes of delay on a line, by cause | `TransitMatters.line_delays` | a day or week |
+| Number of scheduled trips on a route | `TransitMatters.scheduled_service` | a day, week, or month, in `.counts` |
+| Scheduled vs. delivered service hours | `TransitMatters.service_hours` | a day, week, or month |
+| Ridership on a line | `TransitMatters.ridership` | a week |
+| How accurate arrival predictions were | `TransitMatters.time_predictions` | a week |
+
+**Right now, and system-wide.**
+
+| Question | Method |
+| --- | --- |
+| Which alerts are in effect now? | `TransitMatters.current_alerts` |
+| Where are the elevators and escalators? | `TransitMatters.facilities` |
+| Service and ridership across the whole system | `TransitMatters.service_ridership_dashboard` |
+| Is the API healthy? | `TransitMatters.healthcheck` |
+
+## Finding IDs
+
+Each kind of ID has its own format, and some endpoints spell the same line
+differently. Check this table before guessing:
+
+| Parameter | Used by | Looks like |
+| --- | --- | --- |
+| `stop`, `from_stop`, `to_stop` | `headways`, `dwells`, `travel_times`, `aggregate_*` | `"70061"` (rapid transit), `"1-0-110"` (bus), `"CR-Fairmount_0_DB-2205-01"` (commuter rail) |
+| `route`, `route_id` | `historical_alerts`, `scheduled_service`, `time_predictions`, `stops` | `"Red"`, `"66"`, `"CR-Fairmount"`, `"Boat-F1"` |
+| `line` | `line_delays` | `"Red"`, `"CR-Fairmount"` |
+| `line`, `line_id` | `trip_metrics`, `service_hours` | `"line-red"` (lowercase; rapid transit only) |
+| `line_id` | `ridership` | `"line-Red"`, `"line-66"`, `"line-Fairmount"` |
+| `line_id` | `speed_restrictions` | `"line-Red"` (case-sensitive; rapid transit only) |
+
+`TransitMatters.routes` lists every route ID. `TransitMatters.stops` lists the
+stations on a route, with the stop ID of each platform by direction:
+
+```python
+red = tm.stops("Red")
+print(red.direction.to_dict())  # {'0': 'northbound', '1': 'southbound'}
+for station in red.stations[:3]:
+    print(station.stop_name, station.stops.to_dict())
+# Alewife {'0': ['70061'], '1': ['70061']}
+# Davis {'0': ['70064'], '1': ['70063']}
+# Porter {'0': ['70066'], '1': ['70065']}
+```
+
+Platforms have separate IDs for each direction, so `from_stop` and `to_stop`
+must both be platforms for the direction you're traveling. Southbound from
+Davis to Porter is `from_stop="70063", to_stop="70065"`.
+
+A stop ID that doesn't exist isn't an error; you just get an empty list back.
+
+## Working with pandas
+
+Every result is a model object (see `transitmatters.models`), and every model
+has `to_dict()`:
+
+```python
+import pandas as pd
+
+events = tm.headways("2025-03-04", stop="70061")
+df = pd.DataFrame([e.to_dict() for e in events])
+df["current_dep_dt"] = pd.to_datetime(df["current_dep_dt"])
+```
+
+- Timestamps are Eastern local time, formatted `YYYY-MM-DDTHH:MM:SS` with no
+  offset.
+- `to_dict()` uses the API's field names. A few differ from the Python
+  attribute names, e.g. `min` and `25%` instead of `min_` and `field_25`.
+- When a response wraps its list in a field, such as
+  `scheduled_service(...).counts` or `speed_restrictions(...).zones`, build
+  the DataFrame from that field.
+
+## Errors
+
+When the API rejects a request, methods raise `transitmatters.APIError`:
+
+```python
+from transitmatters import APIError
+
+try:
+    tm.stops("Purple")
+except APIError as e:
+    print(e.status_code, e.message)  # 404 Route 'Purple' not found
+```
+
+## Async
+
+`transitmatters.AsyncTransitMatters` has the same methods, as coroutines. It's
+useful for fetching many days at once. In Jupyter you can `await` directly in
+a cell.
+
+```python
+import asyncio
+from transitmatters import AsyncTransitMatters
+
+async def main():
+    async with AsyncTransitMatters() as tm:
+        days = ["2025-03-03", "2025-03-04", "2025-03-05"]
+        return await asyncio.gather(*(tm.headways(d, stop="70061") for d in days))
+
+per_day = asyncio.run(main())
+```
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run python scripts/docs.py  # preview the API docs at http://localhost:8080
+```
+
+The API docs are built from this README and the docstrings in
+`src/transitmatters/`, and are published to GitHub Pages on every push to
+`main`.
+
+`src/transitmatters/_generated/` is generated from the upstream OpenAPI spec by
+`openapi-python-client`; don't edit it by hand. A weekly workflow syncs the
+spec and opens a PR (see `scripts/sync_spec.py`). The public API lives in
+`src/transitmatters/client.py`.

transitmatters-0.1.0/README.md

@@ -0,0 +1,162 @@
+# transitmatters-py
+
+<!-- The API docs include this file from here down. -->
+
+MBTA performance data from the [TransitMatters Data Dashboard](https://dashboard.transitmatters.org),
+as Python objects: travel times, headways, dwells, ridership, service levels,
+delays, speed restrictions, and alerts.
+
+```sh
+pip install transitmatters
+```
+
+```python
+from transitmatters import TransitMatters
+
+tm = TransitMatters()
+
+# Every southbound Red Line trip from Alewife to Braintree on March 4, 2025
+trips = tm.travel_times("2025-03-04", from_stop="70061", to_stop="70105")
+print(trips[0].dep_dt, trips[0].travel_time_sec)
+```
+
+Dates can be `datetime.date` objects or `"YYYY-MM-DD"` strings, and date ranges
+include both ends. Parameters that take IDs accept one string or a list.
+
+## Which method do I want?
+
+**What happened on one day.** Each item is a single event.
+
+| Question | Method | Each item is |
+| --- | --- | --- |
+| How long did trips between two stops take? | `TransitMatters.travel_times` | a trip |
+| How long between departures at a stop? | `TransitMatters.headways` | a departure |
+| How long did vehicles sit at a stop? | `TransitMatters.dwells` | a stop a vehicle made |
+| Which alerts were posted for a route? | `TransitMatters.historical_alerts` | an alert |
+| Where were speed restrictions on a line? | `TransitMatters.speed_restrictions` | a zone, in `.zones` |
+
+**Trends over a date range.** Each item summarizes one day, week, or month.
+
+| Question | Method | Each item is |
+| --- | --- | --- |
+| Travel-time statistics between two stops | `TransitMatters.aggregate_travel_times` | a day |
+| ...also broken down by time of day | `TransitMatters.aggregate_travel_times_v2` | a day, or a 30-minute slot |
+| Headway statistics, bunching, and on-time counts at a stop | `TransitMatters.aggregate_headways` | a day |
+| Dwell-time statistics at a stop | `TransitMatters.aggregate_dwells` | a day |
+| Trip count, speed, and miles for a rapid transit line | `TransitMatters.trip_metrics` | a day, week, or month |
+| Minutes of delay on a line, by cause | `TransitMatters.line_delays` | a day or week |
+| Number of scheduled trips on a route | `TransitMatters.scheduled_service` | a day, week, or month, in `.counts` |
+| Scheduled vs. delivered service hours | `TransitMatters.service_hours` | a day, week, or month |
+| Ridership on a line | `TransitMatters.ridership` | a week |
+| How accurate arrival predictions were | `TransitMatters.time_predictions` | a week |
+
+**Right now, and system-wide.**
+
+| Question | Method |
+| --- | --- |
+| Which alerts are in effect now? | `TransitMatters.current_alerts` |
+| Where are the elevators and escalators? | `TransitMatters.facilities` |
+| Service and ridership across the whole system | `TransitMatters.service_ridership_dashboard` |
+| Is the API healthy? | `TransitMatters.healthcheck` |
+
+## Finding IDs
+
+Each kind of ID has its own format, and some endpoints spell the same line
+differently. Check this table before guessing:
+
+| Parameter | Used by | Looks like |
+| --- | --- | --- |
+| `stop`, `from_stop`, `to_stop` | `headways`, `dwells`, `travel_times`, `aggregate_*` | `"70061"` (rapid transit), `"1-0-110"` (bus), `"CR-Fairmount_0_DB-2205-01"` (commuter rail) |
+| `route`, `route_id` | `historical_alerts`, `scheduled_service`, `time_predictions`, `stops` | `"Red"`, `"66"`, `"CR-Fairmount"`, `"Boat-F1"` |
+| `line` | `line_delays` | `"Red"`, `"CR-Fairmount"` |
+| `line`, `line_id` | `trip_metrics`, `service_hours` | `"line-red"` (lowercase; rapid transit only) |
+| `line_id` | `ridership` | `"line-Red"`, `"line-66"`, `"line-Fairmount"` |
+| `line_id` | `speed_restrictions` | `"line-Red"` (case-sensitive; rapid transit only) |
+
+`TransitMatters.routes` lists every route ID. `TransitMatters.stops` lists the
+stations on a route, with the stop ID of each platform by direction:
+
+```python
+red = tm.stops("Red")
+print(red.direction.to_dict())  # {'0': 'northbound', '1': 'southbound'}
+for station in red.stations[:3]:
+    print(station.stop_name, station.stops.to_dict())
+# Alewife {'0': ['70061'], '1': ['70061']}
+# Davis {'0': ['70064'], '1': ['70063']}
+# Porter {'0': ['70066'], '1': ['70065']}
+```
+
+Platforms have separate IDs for each direction, so `from_stop` and `to_stop`
+must both be platforms for the direction you're traveling. Southbound from
+Davis to Porter is `from_stop="70063", to_stop="70065"`.
+
+A stop ID that doesn't exist isn't an error; you just get an empty list back.
+
+## Working with pandas
+
+Every result is a model object (see `transitmatters.models`), and every model
+has `to_dict()`:
+
+```python
+import pandas as pd
+
+events = tm.headways("2025-03-04", stop="70061")
+df = pd.DataFrame([e.to_dict() for e in events])
+df["current_dep_dt"] = pd.to_datetime(df["current_dep_dt"])
+```
+
+- Timestamps are Eastern local time, formatted `YYYY-MM-DDTHH:MM:SS` with no
+  offset.
+- `to_dict()` uses the API's field names. A few differ from the Python
+  attribute names, e.g. `min` and `25%` instead of `min_` and `field_25`.
+- When a response wraps its list in a field, such as
+  `scheduled_service(...).counts` or `speed_restrictions(...).zones`, build
+  the DataFrame from that field.
+
+## Errors
+
+When the API rejects a request, methods raise `transitmatters.APIError`:
+
+```python
+from transitmatters import APIError
+
+try:
+    tm.stops("Purple")
+except APIError as e:
+    print(e.status_code, e.message)  # 404 Route 'Purple' not found
+```
+
+## Async
+
+`transitmatters.AsyncTransitMatters` has the same methods, as coroutines. It's
+useful for fetching many days at once. In Jupyter you can `await` directly in
+a cell.
+
+```python
+import asyncio
+from transitmatters import AsyncTransitMatters
+
+async def main():
+    async with AsyncTransitMatters() as tm:
+        days = ["2025-03-03", "2025-03-04", "2025-03-05"]
+        return await asyncio.gather(*(tm.headways(d, stop="70061") for d in days))
+
+per_day = asyncio.run(main())
+```
+
+## Development
+
+```sh
+uv sync
+uv run pytest
+uv run python scripts/docs.py  # preview the API docs at http://localhost:8080
+```
+
+The API docs are built from this README and the docstrings in
+`src/transitmatters/`, and are published to GitHub Pages on every push to
+`main`.
+
+`src/transitmatters/_generated/` is generated from the upstream OpenAPI spec by
+`openapi-python-client`; don't edit it by hand. A weekly workflow syncs the
+spec and opens a PR (see `scripts/sync_spec.py`). The public API lives in
+`src/transitmatters/client.py`.

transitmatters-0.1.0/main.py

@@ -0,0 +1,6 @@
+def main():
+    print("Hello from transitmatters-py!")
+
+
+if __name__ == "__main__":
+    main()

transitmatters-0.1.0/openapi-config.yml

@@ -0,0 +1,10 @@
+project_name_override: transitmatters
+package_name_override: _generated
+post_hooks:
+  # Pin the rules: ruff's defaults grew in 0.17, and the generated code can't
+  # be auto-fixed to pass them all, which fails generation.
+  - "ruff check --fix --select E4,E7,E9,F ."
+  - "ruff format ."
+# Put property descriptions on the attributes themselves. Otherwise the generator
+# appends its own "Attributes:" list after the one in the spec's descriptions.
+docstrings_on_attributes: true

transitmatters-0.1.0/pyproject.toml

@@ -0,0 +1,38 @@
+[project]
+name = "transitmatters"
+version = "0.1.0"
+description = "Official Python client for the TransitMatters Data Dashboard API"
+readme = "README.md"
+requires-python = ">=3.13"
+license = "MIT"
+dependencies = [
+    "httpx>=0.27",
+    "attrs>=23.1",
+    "python-dateutil>=2.8",
+]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Repository = "https://github.com/transitmatters/transitmatters-py"
+"Upstream API" = "https://github.com/transitmatters/t-performance-dash"
+
+[dependency-groups]
+dev = [
+    "openapi-python-client",
+    "ruff",
+    "pytest",
+    "pdoc>=16.0.0",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/transitmatters"]
+
+[tool.ruff]
+extend-exclude = ["src/transitmatters/_generated"]

transitmatters-0.1.0/scripts/docs.py

@@ -0,0 +1,42 @@
+#!/usr/bin/env python3
+"""Build or preview the API docs for the transitmatters package with pdoc.
+
+Usage:
+    python scripts/docs.py            # serve at http://localhost:8080, reloading on change
+    python scripts/docs.py -o site    # write static HTML to site/
+
+Takes the same options as the `pdoc` command.
+"""
+
+from __future__ import annotations
+
+import sys
+from collections.abc import Iterator
+
+import pdoc.__main__
+import pdoc.render_helpers
+
+PACKAGE = "transitmatters"
+GENERATED_MODELS = f"{PACKAGE}._generated.models."
+
+_module_candidates = pdoc.render_helpers.module_candidates
+
+
+def module_candidates(identifier: str, current_module: str) -> Iterator[str]:
+    # pdoc links a type only to where it's documented on the current page or
+    # in a parent package of the module that defines it. Models are defined
+    # in transitmatters._generated.models.* but documented in the sibling
+    # transitmatters.models, so without this, return types show their private
+    # path and don't link.
+    yield from _module_candidates(identifier, current_module)
+    if identifier.startswith(GENERATED_MODELS):
+        yield f"{PACKAGE}.models"
+
+
+def main() -> None:
+    pdoc.render_helpers.module_candidates = module_candidates
+    pdoc.__main__.cli([*sys.argv[1:], PACKAGE])
+
+
+if __name__ == "__main__":
+    main()