Install the studio standard's tooling files
Add .ruff.toml, ty.toml, .coveragerc, .pytest.ini and .pre-commit-config.yaml, take .editorconfig, .gitignore and the CI workflow from the standard (keeping the repository's own CI steps, the byte-exact fixture attributes and the fixture ignore exceptions), and reduce pyproject.toml to metadata plus the setuptools build mapping. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B8cL4zN4XpaQF5cBtASzfq
This commit is contained in:
11 files changed
+368
-105
No files matched your search
@@ -1,3 +1,10 @@
|
||||
# Package metadata only, and the build mapping setuptools needs. Tool settings live in their own files:
|
||||
# pixi.toml (environments + tasks), .ruff.toml (lint/format), ty.toml (types), .pytest.ini (tests),
|
||||
# .coveragerc (coverage).
|
||||
# Deviation from the studio standard: setuptools with setuptools-scm instead of hatchling with hatch.toml.
|
||||
# The package maps schemas/, sql/ and vectors/ from the repository root as data subpackages, and takes its
|
||||
# version from git tags.
|
||||
|
||||
[build-system]
|
||||
requires = ["setuptools>=80", "setuptools-scm>=8"]
|
||||
build-backend = "setuptools.build_meta"
|
||||
@@ -40,6 +47,19 @@ Homepage = "https://paperspec.scient.ing"
|
||||
Repository = "https://git.scient.ing/infra/paperspec"
|
||||
Documentation = "https://paperspec.scient.ing/docs/"
|
||||
|
||||
# PEP 735 dependency groups (pip >= 25.1: `pip install -e ".[tools]" --group dev`).
|
||||
# pixi.toml mirrors these for conda-forge environments. The tests need the `tools` extra as well.
|
||||
[dependency-groups]
|
||||
test = ["pytest>=8.4", "pytest-cov>=6", "hypothesis>=6.130"]
|
||||
lint = ["ruff>=0.17.1,<0.18", "ty>=0.0.89,<0.0.90"]
|
||||
dev = [
|
||||
{ include-group = "test" },
|
||||
{ include-group = "lint" },
|
||||
"pre-commit>=4",
|
||||
"build>=1.2",
|
||||
"twine>=6.1",
|
||||
]
|
||||
|
||||
# The code is `src/paperspec`. The schemas, SQL and vectors stay at the repository root, where the
|
||||
# specification links to them and the website serves the schemas at their `$id` URLs, and travel with the
|
||||
# package as data subpackages, so a consumer reads them with importlib.resources. That mapping is why the
|
||||
|
||||
Reference in new issue
Block a user