Bug#1056531: cython 3.x (for Python 3.12)

Julian Gilbey julian at d-and-j.net
Mon Dec 11 19:37:41 GMT 2023


On Mon, Dec 11, 2023 at 08:06:41PM +0100, Matthias Klose wrote:
> > [...]
> > Excellent - I didn't know about that.  Are you OK for me to upload
> > versions of cython and cython-legacy which depend on this to fix the
> > Python 3.12 breakage?
> 
> not for cython, which won't need that soonish for 3.0.x.  and if you have to
> update the b-d to cython3-legacy, why not add the zombie-imp dependency as
> well manually for the few packages that need it?

The problem is not with other packages importing imp (which need to
be fixed in such a case), rather that pyximport (in
cython/cython-legacy) imports imp.  So it's cython that needs to be
patched.

I'm wondering what the provisional timescale for cython 3.0.x is?
Should I just leave my package with an autopkgtest failure until
cython 3.0.x is in unstable or ideally testing?  That's why I was
thinking of also patching cython in the short term until we are ready
for cython 3.0.x to enter unstable.

Best wishes,

   Julian



More information about the debian-science-maintainers mailing list