chore: bump mypyc to v2.3.0 - #202
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be4780d465
ℹ️ 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".
| "setuptools", | ||
| "wheel", | ||
| "mypy[mypyc]==2.1.0", | ||
| "mypy[mypyc]==2.3.0", |
There was a problem hiding this comment.
Pin mypyc to a published release
The exact build-system requirement mypy[mypyc]==2.3.0 is not available, so every isolated PEP 517 build—including pip install . and wheel/sdist builds—fails while resolving build dependencies before setup.py can run. Keep the existing 2.1.0 pin or select another version that is actually published.
Useful? React with 👍 / 👎.
No description provided.