PDFCLOUD-5592 Publish to PyPI - fill out metadata#34
Merged
datalogics-cgreen merged 2 commits intopdfrest:mainfrom Feb 20, 2026
Merged
Conversation
- Updated `readme` entry to include content type. - Added `maintainers`, `keywords`, and `classifiers` fields. - Defined support for Python 3.10 to 3.14 using `requires-python` and `classifiers`. - Added project URLs for homepage, documentation, and source repository. Assisted-by: Codex
- Dropped the `no-build` configuration from `[tool.uv]` in `pyproject.toml`. - Ensures compatibility with updated UV tool requirements. Assisted-by: Codex
✅ Deploy Preview for pdfrest-python ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
datalogics-cgreen
approved these changes
Feb 20, 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
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.
PDFCLOUD-5592
Why this change
Publishing this SDK to PyPI required complete package metadata and a local/release build setup that works consistently. Before this change, key metadata fields were missing from
pyproject.toml, and localuv buildwas blocked by a global UV setting. That increased release friction and reduced package discoverability/quality signals on PyPI.What changed (high level)
The project metadata in
pyproject.tomlwas expanded to align with modern Python packaging guidance: explicit Markdown readme content type, maintainer metadata, keywords, Python-version classifiers, and project URLs (homepage, docs, source).The UV config was also adjusted to remove the global
no-buildbehavior from[tool.uv], so package builds are not disabled for contributors runninguv buildlocally. This keeps dev ergonomics aligned with the release workflow instead of forcing local overrides.Behavior changes
At runtime, SDK API behavior is unchanged.
Packaging behavior changed in two concrete ways:
uv buildsucceeds without--no-config, since build blocking is no longer globally configured in project UV settings.No public SDK interfaces or payload semantics changed.
Validation
Validation focused on packaging/build behavior:
uv build --python 3.11succeeds and produces both sdist and wheel.Limitations:
Risks and follow-ups
Risk is low and scoped to packaging metadata/config.
Notable consideration:
Breaking changes: none.