Conversation
There was a problem hiding this comment.
Pull request overview
Adds uv-based dependency management alongside the existing MkDocs documentation build, and documents a uv-based contributor workflow.
Changes:
- Add
pyproject.toml+uv.lockto supportuv syncfor Python dependencies. - Add a “With uv” contributor page and link it into the MkDocs navigation.
- Add Python tooling niceties (
.python-version, expanded.gitignore) for local development.
Reviewed changes
Copilot reviewed 4 out of 6 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
uv.lock |
Introduces a uv lockfile for reproducible dependency installs. |
pyproject.toml |
Defines project metadata and dependencies for uv-based workflows. |
mkdocs.yml |
Adds nav entry for the new uv contributing guide. |
docs/contributing/with-uv.md |
New contributor documentation for installing/using uv. |
.python-version |
Pins a Python version for local tooling. |
.gitignore |
Ignores common Python build artifacts and .venv. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
pyproject.toml
Outdated
| "python-markdown-math>=0.9", | ||
| ] | ||
|
|
||
|
|
There was a problem hiding this comment.
This repository now has two sources of truth for Python dependencies: requirements.txt (used by Read the Docs) and pyproject.toml/uv.lock (used by uv). Without an explicit sync process, these can drift and lead to different builds; consider generating requirements.txt from the lock (or updating RTD to install via uv) to keep environments consistent.
| [tool.uv] | |
| # This project uses uv as the single source of truth for dependencies. | |
| # The requirements.txt file used by Read the Docs must be generated from | |
| # the uv lockfile to avoid drift between environments. Regenerate it with: | |
| # uv export --format requirements-txt --output requirements.txt |
No description provided.