Ready for Cython 3.1 ?
Hi all, it looks like Cython 3.0.6 is going to be a "most things fixed" kind of release for the 3.0.x release series. Given the work that lies ahead of us for Cython 3.1, I think we're at a point to get started on that, making the future 3.0.x releases stable and "boring". As a reminder, Cython 3.1 will remove support for Python 2.7 and Python 3.[567], i.e. all Python versions that are now EOL. Python 3.8 will continue to receive security fixes for another year. Python 3.7 is EOL but still up for debate since it's probably not hard to support and still maintained in some Linux distributions for another couple of years. But I'm fine with considering it legacy. We'll probably notice if it gets in the way while preparing Cython 3.0, and can leave support in until there's a reason to remove it. https://github.com/cython/cython/issues/2800 I'd like to ease our feature development by using more modern Python features in our code base and by targeting less Python versions in Cython 3.1 compared to the "all things supported" Cython 3.0. I also consider Cython 3.1 a prime target for better Limited API support. Users probably won't care both for that and for outdated Python versions at the same time. Or, they can use Cython 3.0.x for continued legacy support. Since Cython 3.1 is mostly about ripping out old code, we can try to keep the development cycle short, so that new features don't have to wait that long. Certainly not as long as for Cython 3.0… Is everyone and everything ready to start working on Cython 3.1? Stefan
I agree with most of this.
I also consider Cython 3.1 a prime target for better Limited API support.
Yes - but I wouldn't treat complete support as a blocker (I don't think this is what you meant though). There's a separate question about what we consider the minimum viable Limited API version we want to support. I imagine that'll ultimately be decided by "what we can make work", but I don't think it'll be less that 3.4 (when PyType_GetSlot) was added. It's probably something to decide later. David On 05/11/2023 22:06, Stefan Behnel wrote:
Hi all,
it looks like Cython 3.0.6 is going to be a "most things fixed" kind of release for the 3.0.x release series. Given the work that lies ahead of us for Cython 3.1, I think we're at a point to get started on that, making the future 3.0.x releases stable and "boring".
As a reminder, Cython 3.1 will remove support for Python 2.7 and Python 3.[567], i.e. all Python versions that are now EOL. Python 3.8 will continue to receive security fixes for another year. Python 3.7 is EOL but still up for debate since it's probably not hard to support and still maintained in some Linux distributions for another couple of years. But I'm fine with considering it legacy. We'll probably notice if it gets in the way while preparing Cython 3.0, and can leave support in until there's a reason to remove it.
https://github.com/cython/cython/issues/2800
I'd like to ease our feature development by using more modern Python features in our code base and by targeting less Python versions in Cython 3.1 compared to the "all things supported" Cython 3.0.
I also consider Cython 3.1 a prime target for better Limited API support. Users probably won't care both for that and for outdated Python versions at the same time. Or, they can use Cython 3.0.x for continued legacy support.
Since Cython 3.1 is mostly about ripping out old code, we can try to keep the development cycle short, so that new features don't have to wait that long. Certainly not as long as for Cython 3.0…
Is everyone and everything ready to start working on Cython 3.1?
Stefan _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
On Mon, 6 Nov 2023 at 01:19, Stefan Behnel <stefan_ml@behnel.de> wrote:
Hi all,
it looks like Cython 3.0.6 is going to be a "most things fixed" kind of release for the 3.0.x release series.
I'm having issues using CYTHON_LIMITED_API with some Python versions (<=3.9). If you are not in a rush to release 3.0.6, I would like to have some time to properly investigate what's going on. -- Lisandro Dalcin ============ Senior Research Scientist Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/
da-woods schrieb am 06.11.23 um 08:48:
I also consider Cython 3.1 a prime target for better Limited API support.
Yes - but I wouldn't treat complete support as a blocker (I don't think this is what you meant though).
It's experimental in 3.0 and I don't expect it to "fully" work in 3.1.
There's a separate question about what we consider the minimum viable Limited API version we want to support. I imagine that'll ultimately be decided by "what we can make work", but I don't think it'll be less that 3.4 (when PyType_GetSlot) was added. It's probably something to decide later.
That's another thing that moving the support to 3.1 would solve. If we can target Py3.7/3.8+ instead of older versions, then also the Limited API will be more usable. Stefan
Lisandro Dalcin schrieb am 06.11.23 um 09:05:
On Mon, 6 Nov 2023 at 01:19, Stefan Behnel wrote:
it looks like Cython 3.0.6 is going to be a "most things fixed" kind of release for the 3.0.x release series.
I'm having issues using CYTHON_LIMITED_API with some Python versions (<=3.9). If you are not in a rush to release 3.0.6, I would like to have some time to properly investigate what's going on.
I'd rather postpone these things to 3.1. They are not critical for 3.0, and as I wrote, I think it's actually helpful for users to target 3.1 rather than 3.0. Stefan
Stefan Behnel schrieb am 05.11.23 um 23:06:
I'd like to ease our feature development by using more modern Python features in our code base and by targeting less Python versions in Cython 3.1 compared to the "all things supported" Cython 3.0.
I created a 3.0.x maintenance branch and removed the Py<3.7 test jobs from the master branch. That should make the CI response visibly faster. Happy code cleaning :) Stefan
Hi all, There are several PRs targeted to Cython 3.0.X [1]. Is it possible to push all of them or some of them are not ready? At least https://github.com/cython/cython/pull/5754 we can kick of without any doubt. Me personally, I would prefer to include following two PRs: * https://github.com/cython/cython/pull/5785 * https://github.com/cython/cython/pull/5233 Matus [1] https://github.com/cython/cython/pulls?q=is%3Aopen+is%3Apr+milestone%3A3.0.x On Mon, 6 Nov 2023 at 13:56, Stefan Behnel <stefan_ml@behnel.de> wrote:
Stefan Behnel schrieb am 05.11.23 um 23:06:
I'd like to ease our feature development by using more modern Python features in our code base and by targeting less Python versions in Cython 3.1 compared to the "all things supported" Cython 3.0.
I created a 3.0.x maintenance branch and removed the Py<3.7 test jobs from the master branch. That should make the CI response visibly faster.
Happy code cleaning :)
Stefan
_______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
participants (4)
-
da-woods -
Lisandro Dalcin -
matus valo -
Stefan Behnel