-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.13 wheels #80
Comments
I fixed a couple of changes in dependencies and now the package is back in working condition. CI has been changed to build 3.13. I also changed the CI scripts to adapt them to the iminuit ones, so let's see whether that all works. If you have time to help with that, I would appreciate PRs. |
I can take a look. Would you like to use scikit-build-core? I can probably convert to that. |
Yes, but you need to keep the logic which generates the license. I quickly tried to convert and that kept me with the current system. |
Anyway nothing to be done for 3.13 anymore, building the wheels works, I will finish it up. |
Where are you putting the license? Currently there are three spots: trove classifiers (which are the canonical location for license information), a free form field that is really designed just for small snippets of arbitrary text (the long contents get truncated on PyPI, and newlines are technically invalid in the email.message format the metadata is stored in, they are supposed to be converted to a single space), and license files, what are the full text of the license is stored in the wheel metadata directory. If it’s the free text field, that technically can be done, but probably should wait until the dynamic meditate plug-in system is finalized. But that's really not what this field is for. If it’s the files, you can write to that metadata directory with CMake. Though you can also just have as many of them as you like. PEP 639 will redo the license info by requiring an SPDX identifier expression, deprecating the free-form field, and providing a better way to specify which license files go in the metadata directory (but scikit-build-core already lets you do that). So I'd recommend the license text just be an SPDX expression while waiting for things like PyPI to support PEP 639. |
SciPy is now doing this by See https://github.com/scipy/scipy/blob/1adc8cb7a37e09444632a86afea5ee1d07f3e3c5/pyproject.toml#L37-L39 and the |
There are no 3.13 wheels. 3.13.0 has been released.
The text was updated successfully, but these errors were encountered: