Prepare PyPI publishing for springclean#2
Merged
Merged
Conversation
…te README and pyproject.toml
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
Prepares Spring Clean to be published as the
springcleanPython package on PyPI.Changes
springclean-audittospringclean.pyproject.toml.buildandtwineto the development extras.v*tag pushes publish to PyPIManual follow-up after merge
springcleanon TestPyPI and PyPI.testpypiandpypi.pypienvironment.Publishworkflow manually to verify TestPyPI.v0.1.0when ready to publish the real PyPI release.Verification
ruff check .ruff format --check .coverage run -m pytest && coverage reportpython -m buildpython -m twine check dist/*dist/springclean-0.1.0-py3-none-any.whlin a clean virtual environment and checkedspringclean --version/springclean --help