chore: pyproject keyword positioning cleanup#56
Merged
Conversation
…ters classifier, off-positioning) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
rmichaelthomas
added a commit
that referenced
this pull request
Jul 15, 2026
…tioning chore: pyproject keyword positioning cleanup
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
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.
Summary
"programming-language"from thekeywordslist inpyproject.toml. Liminate's locked public-surface terminology never describes the project as a "programming language" — it's a "prose-as-syntax language" — and this PyPI keyword was in tension with that positioning.Topic :: Software Development :: Interpretersclassifier already covers PyPI discovery/categorization, so removal costs no real discoverability. The keyword was redundant with it.classifiersandversionare untouched — this is a single-line metadata edit.Note on file inventory: the spec expected
pyproject.tomlat blob3ac4528; live main has it at0b80941. Diffed the two — the only change is theversion = "0.15.1"→"0.16.0"bump from the most recent commit on main (unrelated wave). Thekeywordsline andclassifiersblock are unchanged from what the spec inspected, so this proceeded as planned.No version bump / release included here — release sequencing (ride the next publish vs. cut 0.16.1) is the architect's call.
Test plan
"programming-language"entry removed; other three keywords preserved in orderclassifiersandversionconfirmed unchanged in the diffrm -rf dist/ build-artifacts && python3 -m buildsucceeds (sdist + wheel)PKG-INFOconfirmed:programming-languageabsent;Keywords: prose-as-syntax,natural-language,interpreterpresent🤖 Generated with Claude Code