Fill in the PyPI metadata before the first real release - #531
Merged
Conversation
The package has never been published, so the metadata that shows on a PyPI page was never exercised: there was no description, so the release would have listed no summary at all; no keywords; no Documentation or Issues link; and the classifiers named neither the supported Python versions nor the subject area. The description and keywords follow CITATION.cff and the README so the three agree. Python classifiers span 3.11 to 3.14, matching requires-python. Part of #436. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mschwamb
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The package has never been published, so the metadata that renders on a PyPI page was never exercised. There was no
description, so a first release would have listed no summary at all; no keywords; no Documentation or Issues link; and the classifiers named neither the supported Python versions nor the subject area.The description and keywords follow
CITATION.cffand the README so the three agree.This is the half of #436 that is still outstanding. The bootstrap leftover (item 2) is already fixed on
main-- it went in with #482, which removes the ~156 MB tarball after untar and sweeps it from older caches, with tests. The other half of #436 needs your PyPI credentials: thelayupname still holds a 1,303-byte0.0.1stub uploaded 2025-01-09, and itsrequires_python >=3.8means pip will not filter it out.Two things I did not touch, both judgement calls:
pip install '.[dev]'installs black 26.5.1 while the pre-commit hook enforces 25.1.0, untouched since April 2025. Dependabot bumps the first and not the second, so a contributor who formats locally uses a different black than the one gating their PR.requires-pythonsays>=3.11and I wrote classifiers to match, but CI only runs 3.13 and 3.14.Closes nothing on its own; part of #436.