Add PyPI packaging and publish workflow #2
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
pyproject.tomlfor PyPI distribution with setuptools build system, zero dependencies, Python 3.8+ support, andcodespyconsole entry pointMANIFEST.into include LICENSE, README.md, and codespy.py in source distributions.github/workflows/publish.ymlGitHub Action to automatically build and publish to PyPI on release using trusted publishers (OIDC)entrypoint.shfor cleaner CI/CD logic--filesflag for scanning specific file lists and addsecurity_score/security_gradeto JSON outputAfter merging, users can install via:
The tool works in three modes:
python3 codespy.py .codespy .python3 -m codespy .Build verified locally:
python -m build --sdist --wheelproducescodespy-1.1.0.tar.gzandcodespy-1.1.0-py3-none-any.whlsuccessfully.Test plan
python -m build --sdist --wheelproduces valid distributionspip install dist/codespy-*.whlinstalls correctlycodespy --versionworks after installpython -m codespy --versionworks after installimport codespy; codespy.__version__works in Python🤖 Generated with Claude Code