Henry Schreiner
Henry Schreiner
IMO we do want at least a pypy-eol, since we don't want people building PyPy wheels for non-supported PyPy versions. Though if PyPy is going away long term, then we...
And CIBW_PROJECT_REQUIRES_PYTHON is not supported in pyproject.toml for projects that don't use PEP 621. That was the main (only) reason to have cpython-eol, otherwise it would have no effect if...
@mattip, thoughts on making old versions or all versions opt-in?
What about this list then:: ``` free-threading prerelease pypy graalpy ``` ?
Couldn't we just require both if that happens? For example, if there was a pypy prerelease, it could be `["pypy", "prerelease"]`? You are basically opting-in, saying you know these exist...
Should we also support opting out? So "!cpython-free-threading" would mean never build free-threading, even if it becomes the default in 3.15/3.26? That would also make these potentially usable before 3.0,...
`cpython-free-threading` vs. `cpython-free-threaded`?
(That actually fits better with `cpython-prerelease` too, same number of dashes)
Try both - it seems like it needs the -L to find it at build time, and the `-rpath` to find it at runtime.
In general, ninja shouldn't be a dependency, build systems should add it dynamically. But this is Django-ninja's fault, we predate them by 4 years and took the PyPI name first....