Repository navigation
publish to PyPI so pip install quicksave works #93
Description
Activity
turns out plain
quicksaveon pypi is already taken by an older unrelated project, so we can't ship under that name. went withquicksave-fsfor the distribution (b2f0029) - the installed command is stillquicksave, sopip install quicksave-fsthen runquicksaveas usual.build is clean locally (
python -m buildproduces quicksave_fs-0.19.0) and the release workflow already has the trusted-publish job gated behind thePYPI_READYvar. remaining bits are one-time and need pypi access:- register github trusted publisher for the
quicksave-fsproject on pypi - set repo variable PYPI_READY=true
- cut a release and it publishes
will update the README install line once it's live.
- register github trusted publisher for the
the workflow side is in now - release.yml has a publish job using trusted publishing (OIDC, no token), gated behind the PYPI_READY repo variable so it stays dormant until the pypi side is ready. pyproject already ships as quicksave-fs since plain quicksave is taken, command stays quicksave.
what's left is the pypi setup itself: add a pending trusted publisher for quicksave-fs on pypi.org (repo qorexdevs/quicksave, workflow release.yml, environment pypi), then flip PYPI_READY to true. next published release will push the wheel + sdist automatically. also added pipx to the readme install section in the meantime
Right now the only way to get quicksave is
pip install git+https://github.com/qorexdevs/quicksaveor grabbing a wheel off the releases page. Putting it on PyPI would make it a plainpip install quicksaveandpipx install quicksave, which is what most people expect from a CLI.What's needed:
quicksavename on PyPI (may already be taken, needs checking)The build already produces clean
quicksave-<ver>-py3-none-any.whland.tar.gz(attached to each release), so the packaging side is mostly done. Happy to take a PR for the workflow, or discuss the trusted-publishing setup here first.