[Cython] Ready for Cython 3.1 ?

da-woods dw-git at d-woods.co.uk
Mon Nov 6 02:48:23 EST 2023


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 at python.org
> https://mail.python.org/mailman/listinfo/cython-devel




More information about the cython-devel mailing list