Skip to content

Prepare Python 1.0.0 release - #7

Merged
mwaisaida-13 merged 1 commit into
mainfrom
release/python-v1.0.0
Sep 10, 2026
Merged

mwaisaida-13 merged 1 commit into
mainfrom
release/python-v1.0.0

Conversation

@mwaisaida-13

Copy link
Copy Markdown
Collaborator

Summary

Prepares the first public Python release. Nothing is published by this PR: the
Private :: Do Not Upload classifier stays in place until the repository is public,
and publishing only runs when a python-v* GitHub Release is created.

  • Bump version to 1.0.0; classifier Development Status :: 5 - Production/Stable.
  • Add python/CHANGELOG.md with the 1.0.0 entry.
  • Add a repository README.md; point the Python README install at PyPI.
  • scripts/python_dev.py: fix stale dev.py references in the docstring, drop the
    hard-coded argparse prog.

Verification

  • python scripts/python_dev.py ci — lint clean, 73 tests passed, wheel + sdist
    built, twine check --strict passed.
  • Test suite run on local 3.10 / 3.12 / 3.13 / 3.14 (3.11 via CI).
  • Built wheel installed in a clean venv: version 1.0.0, --help works, invalid
    input rejected without echoing the value.
  • verify python-v1.0.0 fails only on Private :: Do Not Upload, as intended.

Release steps after merge

  1. Create the pypi GitHub environment (required reviewers) and the PyPI pending
    trusted publisher.
  2. Once the repository is public: remove Private :: Do Not Upload in a follow-up PR.
  3. Publish a GitHub Release tagged python-v1.0.0 to trigger python-release.yml.

- Bump version to 1.0.0 and mark the package Production/Stable. The
  `Private :: Do Not Upload` classifier stays until the repository is public.
- Add python/CHANGELOG.md with the 1.0.0 entry.
- Add a repository README; point the Python README install at PyPI.
- python_dev.py: fix stale dev.py references in the docstring and drop the
  hard-coded argparse prog name.
@mwaisaida-13
mwaisaida-13 merged commit c8e5580 into main Sep 10, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants