Conversation
Define the console entry point in modern project metadata and document zero-install uvx usage.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 623d9b13d9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,32 @@ | |||
| [build-system] | |||
There was a problem hiding this comment.
On every release, both actions/setup-python@v2 steps in .github/workflows/publish.yml still use cache-dependency-path: '**/setup.py'. The pip-cache setup errors when that pattern matches no files, so replacing setup.py with this file causes the release workflow to stop before its tests or build run; point those entries at pyproject.toml as part of the migration.
Useful? React with 👍 / 👎.
| @@ -0,0 +1,32 @@ | |||
| [build-system] | |||
| requires = ["setuptools>=77"] | |||
There was a problem hiding this comment.
For Python 3.6–3.8, which remain in both CI matrices, a source installation cannot create its isolated build environment because Setuptools 77 and newer require Python 3.9+. Published wheels may hide this, but pip install --no-binary, installs from an sdist, and source checkouts on those tested interpreters fail before building; either use a compatible backend requirement or explicitly raise the project's supported Python version and update the matrices.
Useful? React with 👍 / 👎.
Use setup-python v6 throughout CI and hash pyproject.toml for the release pip cache. Previously the release workflow referenced the removed setup.py file and could fail before tests or publishing.
Declare the supported interpreter floor and align release testing and publishing with Python 3.12-3.14. Previously the package metadata implicitly allowed versions that cannot install the build backend.
1 participant
Summary
setup.pywith a modernpyproject.tomlconfigurationuvTesting