A new release is needed in order to publish wheels for CPython 3.15.
I already merged #589 which added it to our build matrix.
I also want to note that #511 would help make this a non-problem for GIL-enabled builds as well as vastly reduce the number of artifacts we need to publish to support all current versions of CPython as well as future ones. I also plan to explore the recently standardised abi3t to also fix this yearly point of friction for free-threaded builds, though the ecosystem (setuptools in particular) isn't ready yet.
If for any reason we didn't include #511 in our next release, I would also love feedback on wether we could/should drop support for 3.10, which will be EOL in a little less than a month. I don't know of a motivation to do so right now, other than reducing the number of wheels, which #511 would be much more effecient at.
A new release is needed in order to publish wheels for CPython 3.15.
I already merged #589 which added it to our build matrix.
I also want to note that #511 would help make this a non-problem for GIL-enabled builds as well as vastly reduce the number of artifacts we need to publish to support all current versions of CPython as well as future ones. I also plan to explore the recently standardised
abi3tto also fix this yearly point of friction for free-threaded builds, though the ecosystem (setuptools in particular) isn't ready yet.If for any reason we didn't include #511 in our next release, I would also love feedback on wether we could/should drop support for 3.10, which will be EOL in a little less than a month. I don't know of a motivation to do so right now, other than reducing the number of wheels, which #511 would be much more effecient at.