3phi-framework 0.2.5__tar.gz

3phi_framework-0.2.5/.env

@@ -0,0 +1,11 @@
+# object storage
+S3_ENDPOINT_URL=http://localhost:19000
+S3_ACCESS_KEY=minioadmin
+S3_SECRET_KEY=minioadmin
+# db connection
+DB_TYPE=POSTGRES
+DB_USER=postgres
+DB_PASSWORD=password
+DB_NAME=3phi-db
+DB_HOST=localhost
+DB_PORT=5432

3phi_framework-0.2.5/.github/workflows/docs.yml

@@ -0,0 +1,53 @@
+name: Build and deploy Sphinx docs
+
+on:
+  push:
+    branches: [ main ]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install deps
+        run: |
+          python -m pip install --upgrade pip
+          pip install -r docs/requirements.txt
+          pip install -e .
+
+      - name: Build HTML
+        run: |
+          sphinx-build -b html -W --keep-going -T docs docs/_build/html
+
+      - name: Configure Pages
+        uses: actions/configure-pages@v5
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: docs/_build/html
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

3phi_framework-0.2.5/.gitignore

@@ -0,0 +1,10 @@
+.idea
+dist
+**/__pycache__/
+src/3phi_framework.egg-info
+.DS_Store
+docs/_build
+docker/tmp
+docker/db/init/3_db_seed.sql
+docker/object_storage/*
+**.bak

3phi_framework-0.2.5/.gitlab/merge_request_templates/mr-template.md

@@ -0,0 +1,10 @@
+## Summary
+Why is this change needed?
+
+## Issue Link
+<put link here or remove if not available>
+
+## Checklist
+- [ ] Linked issue if available
+- [ ] Updated README.md
+- [ ] No sensitive data

3phi_framework-0.2.5/.gitlab-ci.yml

@@ -0,0 +1,106 @@
+stages: [lint, style, build, publish]
+image: python:3.12
+
+variables:
+  PIP_DISABLE_PIP_VERSION_CHECK: "1"
+  PIP_NO_CACHE_DIR: "1"
+  # Ensure tags are available to the job
+  GIT_STRATEGY: fetch
+  GIT_DEPTH: "0"
+
+# ---------- Ruff lint and format with MR annotations ----------
+.ruff:
+  image: python:3.11-slim
+  before_script:
+    - python -V
+    - pip install --no-cache-dir ruff==0.6.8
+
+ruff_lint:
+  extends: .ruff
+  stage: lint
+  rules:
+    - when: always
+  script:
+    - ruff check --output-format=junit --output-file=ruff-junit.xml .
+  artifacts:
+    when: always
+    reports:
+      junit: ruff-junit.xml
+
+ruff_format_check:
+  extends: .ruff
+  stage: style
+  rules:
+    - when: always
+  script:
+    - ruff format --check .
+
+# ---------- Release (tag) ----------
+build_release:
+  stage: build
+  needs: [ruff_lint, ruff_format_check]
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  script:
+    - |
+      python -m pip install -U pip build
+      python -m build
+  artifacts:
+    when: always
+    paths:
+      - dist/
+
+publish_release:
+  stage: publish
+  needs: [build_release]
+  rules:
+    - if: '$CI_COMMIT_TAG'
+  script:
+    - |
+      python -m pip install -U twine
+      TWINE_USERNAME=gitlab-ci-token TWINE_PASSWORD="$CI_JOB_TOKEN" \
+      python -m twine upload \
+        --repository-url "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/pypi" \
+        dist/*
+
+# ---------- Manual PR build (dev) ----------
+build_pr_manual:
+  stage: build
+  needs: [ruff_lint, ruff_format_check]
+  rules:
+    - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
+      when: always
+  script:
+    - |
+      python -m pip install -U pip build
+      # Ensure we have tags (safety if runner ignores GIT_DEPTH)
+      git fetch --force --prune --tags
+      # Get latest semver-like tag (vX.Y.Z or X.Y.Z); fallback to 0.0.0
+      BASE_TAG="$(git tag --list --sort=-v:refname | grep -E '^(v)?[0-9]+\.[0-9]+\.[0-9]+$' | head -n1 || true)"
+      if [ -z "$BASE_TAG" ]; then
+        BASE_VERSION="0.0.0"
+      else
+        BASE_VERSION="${BASE_TAG#v}"   # strip leading v if present
+      fi
+      export SETUPTOOLS_SCM_PRETEND_VERSION="${BASE_VERSION}.dev${CI_PIPELINE_IID}+pr.${CI_MERGE_REQUEST_IID}.sha${CI_COMMIT_SHORT_SHA}"
+      echo "Building version: $SETUPTOOLS_SCM_PRETEND_VERSION"
+      python -m build
+  artifacts:
+    when: always
+    expire_in: 7 days
+    paths:
+      - dist/
+
+publish_pr_manual:
+  stage: publish
+  needs: [build_pr_manual]
+  rules:
+    - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
+      when: manual
+  script:
+    - |
+      python -m pip install -U twine
+      TWINE_USERNAME=gitlab-ci-token TWINE_PASSWORD="$CI_JOB_TOKEN" \
+      python -m twine upload \
+        --repository-url "${CI_API_V4_URL}/projects/${CI_PROJECT_ID}/packages/pypi" \
+        dist/*

3phi_framework-0.2.5/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.14.1
+    hooks:
+      - id: ruff-check
+        args: [--fix, --exit-non-zero-on-fix, --diff]
+      - id: ruff-format

3phi_framework-0.2.5/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.4
+Name: 3phi-framework
+Version: 0.2.5
+Summary: Framework for 3phi project
+Author-email: Christian Fotteler <chris@inilab.dk>
+License: MIT
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# 3phi Framework
+
+Utility classes for **DB** access, **S3** interactions, and **data processing** via a `DataExtractor`.  
+Distributed privately via GitLab’s Package Registry (private PyPI).
+
+> **Install name:** `3phi-framework`  
+> **Import package:** `threephi_framework`
+
+---
+
+## Features (MVP)
+
+- **DBConnector** – simple connector + query helpers.
+- **S3Connector** – upload/download and safe path helpers.
+- **DataExtractor** – API to interact with the Data in S3.
+
+> This is an early version. API may evolve until `v1.0`. See “Versioning” below.
+
+---
+
+## Requirements
+
+- Python **3.9+**
+- Access to the GitLab **Package Registry** for this project or group.
+
+---
+
+## Build a new version
+
+Write & commit your code and then tag it:
+```
+git tag -a vx.x.x -m "vx.x.x"
+git push --tags
+```
+
+
+## Installation (GitLab private PyPI)
+
+Create a **Deploy Token** with scope `read_package_registry` in this project.
+
+```bash
+pip install \
+  --index-url "https://<DEPLOY_USER>:<DEPLOY_TOKEN>@gitlab.com/api/v4/projects/<PROJECT_ID>/packages/pypi/simple" \
+  3phi-framework
+```
+
+### Other ways to install 
+Replace placeholders like <PROJECT_ID>, <USERNAME>, <TOKEN>, and use the gitlab domain (gitlab.3pi-dev.io).
+
+1) Quick one-liner (private project, for code completion etc.)
+
+Use a Deploy Token (Settings → Repository → Deploy tokens) with read_package_registry, or a PAT with read_api.
+```
+# safer: export creds so they don't land in shell history
+export GL_USER="gitlab+deploy-token-<id>"   # or your GitLab username if using a PAT
+export GL_TOKEN="<token>"
+
+pip install \
+  --index-url "https://$GL_USER:$GL_TOKEN@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple" \
+  --extra-index-url "https://pypi.org/simple" \
+  3phi-framework==0.1.2
+```
+Package name to install: 3phi-framework
+Module you import: threephi_framework
+--extra-index-url https://pypi.org/simple lets pip resolve any third-party deps from PyPI.
+
+2) Put it in requirements.txt (useful for docker image builds)
+
+At the top of requirements.txt:
+```
+--index-url https://<USER>:<TOKEN>@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple
+--extra-index-url https://pypi.org/simple
+3phi-framework==0.1.2
+```
+Then install as you normally would.
+
+3) Persist credentials in pip.conf (developer machines)
+
+Linux/macOS: ~/.pip/pip.conf
+Windows: %APPDATA%\pip\pip.ini
+```
+[global]
+index-url = https://<USER>:<TOKEN>@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple
+extra-index-url = https://pypi.org/simple
+```
+Then you can just:
+```
+pip install 3phi-framework==0.1.2
+```
+
+---
+
+## Quickstart
+
+The framework is set up for local development as well as for being used in a deployment.
+To set up your environment for local development, follow these steps:
+
+### Set up virtual environment
+
+[execute_data_app.sh](execute_data_app.sh) expects a virtual environment to be set up under [.venv]. See the [python docs](https://docs.python.org/3/library/venv.html) on how to set it up.
+
+### Seed data
+
+Obtain seed data for the database and the object storage and copy it to:
+- [3_db_seed.sql](docker/db/init/3_db_seed.sql): This should be a sql dump/snapshot of a working 3phi Database, PSQL will automatically seed the DB when it is created using docker compose.
+- [3phi](docker/object_storage/3phi): This should be a copy of a bucket from a working object storage. It will be mounted in the minio object storage as a bucket.
+
+### Spin up DB and Object Storage
+
+Navigate to [docker](./docker) and run `docker compose up -d`.
+This will bring up a local DB and a MinIO Object Storage seeded with the data you provided.
+
+### Run a data app locally
+
+Use the utility script [execute_data_app.sh](execute_data_app.sh) and pass the data app name as an argument, e.g.:
+```
+./exectue_data_app.sh sm_classifier
+```
+In case the script is not executable, make it executable:
+```
+chmod +x execute_data_app.sh
+```
+
+The script will install the dependencies in [requirements.txt](requirements.txt) in your virtual environment, set up environment variables as they are listed in [.env](.env) and execute the data app as a python module.
+
+## Contibuting to 3phi Framework
+
+The framework is currently not open-source, but the aim is to open-source it eventually.
+
+### Commit Message Guidelines
+
+Commit Messages should follow the recommendations of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), supplemented by the [Angular Convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines). Every commit must contain `type` and `description`, while `scope`, `body` and `footer` are optional:
+
+```
+<type>(<scope>): <description>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+#### Type
+`type` is mandatory, and should be one of the following:
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `build`: Changes that affect the build system or external dependencies
+- `ci`: Changes to our CI configuration files and scripts
+- `docs`: Documentation only changes
+- `perf`: A code change that improves performance
+- `refactor`: A code change that neither fixes a bug nor adds a feature
+- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- `test`: Adding missing tests or correcting existing tests
+
+#### Scope
+`scope`is optional, but if included it should be a noun that gives context to the part of the codebase that is affected by the commit. Please do not use issue identifiers as scope.
+
+#### Description
+`description` is mandatory, and provides a short and concise description of the change. Be mindful of the following:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+#### Body
+`body` is optional, but if included, it should use the imperative, present tense: "change" not "changed" nor "changes" (just as in `description`). The body should include the motivation for the change and contrast this with previous behavior.
+
+#### Footer
+`footer` is optional, but if included, it should use `-`in place of whitespace to distinguish it from a `body`or multiline `body`. It is the place to reference git issues that this commit closes.
+
+#### Breaking Change
+A commit that make incompatible API changes, should be denoted `Breaking Change`, either by a `!` right after `scope` or by adding `Breaking Change` or `Breaking-Change` to `footer`.
+
+### Linter and formatter
+[Ruff](https://docs.astral.sh/ruff/linter/) is used for linting and formatting in both local development (pre-commit) and CI, with a shared configuration in pyproject.toml.
+
+#### Ruff in CI pipeline
+- Runs on pushes/merge requests in GitLab.
+- Checks only (no auto-fix). If any check fails, the pipeline fails and the change cannot be merged.
+
+#### Ruff in pre-commit hook
+- Runs locally on commit (and optionally on push).
+- Applies fixes and then fails if it changed files so you can review and commit the updates.
+- First-time setup:
+  ```
+  pre-commit install
+  # optional: also run on push
+  pre-commit install --hook-type pre-push
+  ```
+- Manual sweep of the whole repo:
+  ```
+  pre-commit run --all-files
+  ```
+
+
+## Documentation
+
+This Project uses Sphinx for API docs. From the [docs](./docs/) run:
+```
+make html
+```
+to generate the docs. Then you can open the [docs index](./docs/_build/html/index.html) in your browser.
+
+We leverage [autodoc](https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html) to generate the documentation from docstrings in code.
+To configure which classes are included in the API docs, edit and extend [index.rst](./docs/api/index.rst).

3phi_framework-0.2.5/README.md

@@ -0,0 +1,205 @@
+# 3phi Framework
+
+Utility classes for **DB** access, **S3** interactions, and **data processing** via a `DataExtractor`.  
+Distributed privately via GitLab’s Package Registry (private PyPI).
+
+> **Install name:** `3phi-framework`  
+> **Import package:** `threephi_framework`
+
+---
+
+## Features (MVP)
+
+- **DBConnector** – simple connector + query helpers.
+- **S3Connector** – upload/download and safe path helpers.
+- **DataExtractor** – API to interact with the Data in S3.
+
+> This is an early version. API may evolve until `v1.0`. See “Versioning” below.
+
+---
+
+## Requirements
+
+- Python **3.9+**
+- Access to the GitLab **Package Registry** for this project or group.
+
+---
+
+## Build a new version
+
+Write & commit your code and then tag it:
+```
+git tag -a vx.x.x -m "vx.x.x"
+git push --tags
+```
+
+
+## Installation (GitLab private PyPI)
+
+Create a **Deploy Token** with scope `read_package_registry` in this project.
+
+```bash
+pip install \
+  --index-url "https://<DEPLOY_USER>:<DEPLOY_TOKEN>@gitlab.com/api/v4/projects/<PROJECT_ID>/packages/pypi/simple" \
+  3phi-framework
+```
+
+### Other ways to install 
+Replace placeholders like <PROJECT_ID>, <USERNAME>, <TOKEN>, and use the gitlab domain (gitlab.3pi-dev.io).
+
+1) Quick one-liner (private project, for code completion etc.)
+
+Use a Deploy Token (Settings → Repository → Deploy tokens) with read_package_registry, or a PAT with read_api.
+```
+# safer: export creds so they don't land in shell history
+export GL_USER="gitlab+deploy-token-<id>"   # or your GitLab username if using a PAT
+export GL_TOKEN="<token>"
+
+pip install \
+  --index-url "https://$GL_USER:$GL_TOKEN@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple" \
+  --extra-index-url "https://pypi.org/simple" \
+  3phi-framework==0.1.2
+```
+Package name to install: 3phi-framework
+Module you import: threephi_framework
+--extra-index-url https://pypi.org/simple lets pip resolve any third-party deps from PyPI.
+
+2) Put it in requirements.txt (useful for docker image builds)
+
+At the top of requirements.txt:
+```
+--index-url https://<USER>:<TOKEN>@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple
+--extra-index-url https://pypi.org/simple
+3phi-framework==0.1.2
+```
+Then install as you normally would.
+
+3) Persist credentials in pip.conf (developer machines)
+
+Linux/macOS: ~/.pip/pip.conf
+Windows: %APPDATA%\pip\pip.ini
+```
+[global]
+index-url = https://<USER>:<TOKEN>@gitlab.3pi-dev.io/api/v4/projects/<PROJECT_ID>/packages/pypi/simple
+extra-index-url = https://pypi.org/simple
+```
+Then you can just:
+```
+pip install 3phi-framework==0.1.2
+```
+
+---
+
+## Quickstart
+
+The framework is set up for local development as well as for being used in a deployment.
+To set up your environment for local development, follow these steps:
+
+### Set up virtual environment
+
+[execute_data_app.sh](execute_data_app.sh) expects a virtual environment to be set up under [.venv]. See the [python docs](https://docs.python.org/3/library/venv.html) on how to set it up.
+
+### Seed data
+
+Obtain seed data for the database and the object storage and copy it to:
+- [3_db_seed.sql](docker/db/init/3_db_seed.sql): This should be a sql dump/snapshot of a working 3phi Database, PSQL will automatically seed the DB when it is created using docker compose.
+- [3phi](docker/object_storage/3phi): This should be a copy of a bucket from a working object storage. It will be mounted in the minio object storage as a bucket.
+
+### Spin up DB and Object Storage
+
+Navigate to [docker](./docker) and run `docker compose up -d`.
+This will bring up a local DB and a MinIO Object Storage seeded with the data you provided.
+
+### Run a data app locally
+
+Use the utility script [execute_data_app.sh](execute_data_app.sh) and pass the data app name as an argument, e.g.:
+```
+./exectue_data_app.sh sm_classifier
+```
+In case the script is not executable, make it executable:
+```
+chmod +x execute_data_app.sh
+```
+
+The script will install the dependencies in [requirements.txt](requirements.txt) in your virtual environment, set up environment variables as they are listed in [.env](.env) and execute the data app as a python module.
+
+## Contibuting to 3phi Framework
+
+The framework is currently not open-source, but the aim is to open-source it eventually.
+
+### Commit Message Guidelines
+
+Commit Messages should follow the recommendations of [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), supplemented by the [Angular Convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines). Every commit must contain `type` and `description`, while `scope`, `body` and `footer` are optional:
+
+```
+<type>(<scope>): <description>
+<BLANK LINE>
+<body>
+<BLANK LINE>
+<footer>
+```
+
+#### Type
+`type` is mandatory, and should be one of the following:
+
+- `feat`: A new feature
+- `fix`: A bug fix
+- `build`: Changes that affect the build system or external dependencies
+- `ci`: Changes to our CI configuration files and scripts
+- `docs`: Documentation only changes
+- `perf`: A code change that improves performance
+- `refactor`: A code change that neither fixes a bug nor adds a feature
+- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- `test`: Adding missing tests or correcting existing tests
+
+#### Scope
+`scope`is optional, but if included it should be a noun that gives context to the part of the codebase that is affected by the commit. Please do not use issue identifiers as scope.
+
+#### Description
+`description` is mandatory, and provides a short and concise description of the change. Be mindful of the following:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+#### Body
+`body` is optional, but if included, it should use the imperative, present tense: "change" not "changed" nor "changes" (just as in `description`). The body should include the motivation for the change and contrast this with previous behavior.
+
+#### Footer
+`footer` is optional, but if included, it should use `-`in place of whitespace to distinguish it from a `body`or multiline `body`. It is the place to reference git issues that this commit closes.
+
+#### Breaking Change
+A commit that make incompatible API changes, should be denoted `Breaking Change`, either by a `!` right after `scope` or by adding `Breaking Change` or `Breaking-Change` to `footer`.
+
+### Linter and formatter
+[Ruff](https://docs.astral.sh/ruff/linter/) is used for linting and formatting in both local development (pre-commit) and CI, with a shared configuration in pyproject.toml.
+
+#### Ruff in CI pipeline
+- Runs on pushes/merge requests in GitLab.
+- Checks only (no auto-fix). If any check fails, the pipeline fails and the change cannot be merged.
+
+#### Ruff in pre-commit hook
+- Runs locally on commit (and optionally on push).
+- Applies fixes and then fails if it changed files so you can review and commit the updates.
+- First-time setup:
+  ```
+  pre-commit install
+  # optional: also run on push
+  pre-commit install --hook-type pre-push
+  ```
+- Manual sweep of the whole repo:
+  ```
+  pre-commit run --all-files
+  ```
+
+
+## Documentation
+
+This Project uses Sphinx for API docs. From the [docs](./docs/) run:
+```
+make html
+```
+to generate the docs. Then you can open the [docs index](./docs/_build/html/index.html) in your browser.
+
+We leverage [autodoc](https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html) to generate the documentation from docstrings in code.
+To configure which classes are included in the API docs, edit and extend [index.rst](./docs/api/index.rst).

3phi_framework-0.2.5/docker/clean_volume.sh

@@ -0,0 +1,3 @@
+#!/bin/bash
+rm -rf ./tmp/pgdata
+mkdir ./tmp/pgdata

3phi_framework-0.2.5/docker/db/init/1_debug.sh

@@ -0,0 +1,3 @@
+# ./db/init/debug.sh
+#!/bin/bash
+echo "✅ DB INIT SCRIPT IS RUNNING"

3phi_framework-0.2.5/docker/db/init/2_add_user.sql

@@ -0,0 +1 @@
+CREATE ROLE "threephi_db_user" WITH LOGIN NOSUPERUSER NOCREATEDB NOCREATEROLE INHERIT NOREPLICATION PASSWORD 'userpass';

3phi_framework-0.2.5/docker/docker-compose.yml

@@ -0,0 +1,33 @@
+services:
+
+  local-db:
+    container_name: local-3phi-db
+    image: postgres:18-alpine
+    environment:
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: password
+      POSTGRES_DB: 3phi-db
+    ports:
+      - "5432:5432"
+    volumes:
+     - ./tmp/pgdata:/var/lib/postgresql
+     - ./db/init:/docker-entrypoint-initdb.d
+
+  local-object-storage:
+    container_name: local-minio
+    image: minio/minio:latest
+    command: server /data --console-address ":9001"
+    ports:
+      - "19000:9000"
+      - "19001:9001"
+    environment:
+      MINIO_ROOT_USER: minioadmin
+      MINIO_ROOT_PASSWORD: minioadmin
+    volumes:
+      - ./object_storage:/data
+    healthcheck:
+      test: [ "CMD", "curl", "-f", "http://localhost:9000/minio/health/ready" ]
+      interval: 5s
+      timeout: 3s
+      retries: 20
+    restart: unless-stopped

3phi_framework-0.2.5/docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = .
+BUILDDIR      = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)