Files
zeekayandHanzo Dev e65cdec46a one place says what this package is
pyproject carried a [tool.poetry] table that nothing read — setuptools.build_meta
takes its metadata from setup.py, and no workflow, script or Makefile here
invokes poetry. It disagreed with setup.py on both facts that matter: version
1.0.0 against 1.0.1, and python >=3.14 against >=3.8. A reader checking the
version was more likely to find the dead answer than the live one.

The tree is still behind PyPI, which serves 1.1.1 against this 1.0.1. That is
left alone deliberately: bumping past it would publish this code as newer than
something it may well be older than. Someone needs to reconcile which tree is
current before this package moves again.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-18 21:41:01 -07:00

11 lines
593 B
TOML

# Build only. Package metadata lives in setup.py, which is what
# setuptools.build_meta reads — the [tool.poetry] table that used to sit here
# was read by nothing (no workflow, script or Makefile in this repo invokes
# poetry) and disagreed with setup.py on the two facts that matter: it named
# version 1.0.0 against setup.py's 1.0.1, and python >=3.14 against >=3.8. A
# second set of metadata that no build consults is a second answer to every
# question and the one a reader is more likely to find first.
[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"