Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #15317 > unrolled thread

cython 3.x (for Python 3.12)

Back to article view | Back to linux.debian.maint.python

Contents

  cython 3.x (for Python 3.12) Stefano Rivera <stefanor@debian.org> - 2023-11-25 17:30 +0100
    Re: cython 3.x (for Python 3.12) Stefano Rivera <stefanor@debian.org> - 2023-11-25 17:50 +0100
    Re: cython 3.x (for Python 3.12) julien.puydt@gmail.com - 2023-11-26 21:30 +0100
    Re: cython 3.x (for Python 3.12) julien.puydt@gmail.com - 2023-11-30 08:30 +0100
      Re: cython 3.x (for Python 3.12) julien.puydt@gmail.com - 2023-12-12 09:20 +0100
    Re: cython 3.x (for Python 3.12) Julian Gilbey <julian@d-and-j.net> - 2023-11-30 22:20 +0100
    Re: cython 3.x (for Python 3.12) Julian Gilbey <jdg@debian.org> - 2023-12-10 21:20 +0100
      Re: cython 3.x (for Python 3.12) Andrey Rakhmatullin <wrar@wrar.name> - 2023-12-10 21:40 +0100
        Re: cython 3.x (for Python 3.12) Andrey Rakhmatullin <wrar@wrar.name> - 2023-12-10 21:40 +0100
          Re: cython 3.x (for Python 3.12) Matthias Klose <doko@debian.org> - 2023-12-11 08:10 +0100
            Re: cython 3.x (for Python 3.12) Matthias Klose <doko@debian.org> - 2023-12-11 09:50 +0100
            Re: cython 3.x (for Python 3.12) Julian Gilbey <julian@d-and-j.net> - 2023-12-11 11:30 +0100
            Re: cython 3.x (for Python 3.12) Matthias Klose <doko@debian.org> - 2023-12-11 16:40 +0100
              Re: cython 3.x (for Python 3.12) Julian Gilbey <julian@d-and-j.net> - 2023-12-11 20:00 +0100
                Re: cython 3.x (for Python 3.12) Matthias Klose <doko@debian.org> - 2023-12-11 20:10 +0100
    Re: cython 3.x (for Python 3.12) Julian Gilbey <julian@d-and-j.net> - 2023-12-12 20:00 +0100

#15317 — cython 3.x (for Python 3.12)

As part of preparing for Python 3.12 in Debian, I've uploaded cython 3
to experimental.

I did some test-building of reverse dependencies, and quite a lot of
them fail.

Out of 291 packages that build-depend on cython3:
    104  attempted     <- FTBFS
      6  given-back    <- build-deps aren't installable
      1  skipped       <- not for arm64
    180  successful
https://people.debian.org/~stefanor/cython3/cython-3.0.5/summary.txt
https://people.debian.org/~stefanor/cython3/cython-3.0.5/stats.txt

I re-tried those "attempted" failures, with cython 0.29.36 to find the
regressions and:
     32  attempted
      1  given-back
     71  successful
https://people.debian.org/~stefanor/cython3/cython-0.29.36/summary.txt
https://people.debian.org/~stefanor/cython3/cython-0.29.36/stats.txt

So, that's 71 regressions with cython3. dd-list below. Please help us
port to cython 3. If this isn't possible, Graham is preparing a
cython-legacy package, to help the stragglers. But we're expecting that
this won't have great Python 3.12 support...
https://ftp-master.debian.org/new/cython-legacy_0.29.36-1~exp1.html

Stefano

Regression dd-list:

Adrian Vondendriesch <adrian.vondendriesch@credativ.de>
   peewee (U)

Alastair McKinstry <mckinstry@debian.org>
   adios

Andreas Tille <tille@debian.org>
   atropos (U)
   macs (U)
   python-cykhash (U)
   python-cytoolz (U)
   python-skbio (U)
   python-srsly (U)
   python-thinc (U)
   tombo (U)

Anton Gladky <gladk@debian.org>
   sfepy (U)

Antonio Valentino <antonio.valentino@tiscali.it>
   cyarray (U)
   pysph (U)
   python-ltfatpy (U)
   pyzoltan (U)

B. Clausius <barcc@gmx.de>
   pybik (U)

Bastian Venthur <venthur@debian.org>
   kivy (U)

Benjamin Drung <bdrung@ubuntu.com>
   rdma-core

Boyuan Yang <byang@debian.org>
   py-libzfs (U)

ChangZhuo Chen (陳昌倬) <czchen@debian.org>
   python-feather-format (U)

Dean Serenevy <dean@serenevy.net>
   kivy (U)

Debian Astro Team <debian-astro-maintainers@lists.alioth.debian.org>
   healpy
   montage
   pyregion

Debian Fonts Task Force <debian-fonts@lists.debian.org>
   compreffor
   pyclipper

Debian Games Team <pkg-games-devel@lists.alioth.debian.org>
   pygame-sdl2
   python-sfml

Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
   atropos
   cyvcf2
   macs
   nipy
   python-cykhash
   python-skbio
   tombo

Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
   pyliblo

Debian PaN Maintainers <debian-pan-maintainers@alioth-lists.debian.net>
   opentsne

Debian Python Modules Team <team+python@tracker.debian.org>
   fpylll

Debian Python Team <team+python@tracker.debian.org>
   azure-uamqp-python
   indexed-gzip
   kivy
   mayavi2
   numpy (U)
   peewee
   py-libzfs
   pybik
   pymssql
   pyreadstat (U)
   pystemmer
   python-cassandra-driver
   python-cytoolz
   python-feather-format
   python-hidapi
   python-line-profiler
   python-llfuse (U)
   python-openstep-plist
   python-pcl
   python-pomegranate
   python-srsly
   python-stack-data
   python-thriftpy
   uvloop (U)

Debian QA Group <packages@qa.debian.org>
   xmms2

Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org>
   cyarray
   gensim
   h5py
   libgpuarray
   mpi4py-fft
   opentsne (U)
   petsc4py
   pyfftw
   pysph
   python-ltfatpy
   python-thinc
   pyzoltan
   sfepy
   statsmodels

Debian Science Team <debian-science-maintainers@lists.alioth.debian.org>
   cypari2
   pandas
   pplpy

Debian ZFS on Linux maintainers <pkg-zfsonlinux-devel@alioth-lists.debian.net>
   py-libzfs (U)

Debichem Team <debichem-devel@lists.alioth.debian.org>
   mdtraj

Diane Trout <diane@ghic.org>
   statsmodels (U)

Drew Parsons <dparsons@debian.org>
   mdtraj (U)
   mpi4py-fft (U)
   petsc4py (U)

Emmanuel Arias <eamanu@debian.org>
   python-cassandra-driver (U)

Free Ekanayaka <freee@debian.org>
   pyliblo (U)

Gard Spreemann <gspr@nonempty.org>
   gudhi
   python-pyspike

Geoffrey Thomas <geofft@ldpreload.com>
   pymssql (U)

Ghislain Antony Vaillant <ghisvail@gmail.com>
   h5py (U)
   libgpuarray (U)
   pyfftw (U)
   python-line-profiler (U)

Gianfranco Costamagna <locutusofborg@debian.org>
   python-esmre

Gijs Molenaar <gijs@pythonic.nl>
   montage (U)

Gordon Ball <gordon@chronitis.net>
   python-stack-data (U)

gtkpod Maintainers <pkg-gtkpod-devel@alioth-lists.debian.net>
   libimobiledevice

Hilko Bengen <bengen@debian.org>
   python-acora

James Cowgill <jcowgill@debian.org>
   python-sfml (U)

Jaromír Mikeš <mira.mikes@seznam.cz>
   pyliblo (U)

Jeremy Bicha <jbicha@debian.org>
   compreffor (U)
   pyclipper (U)

Jerome Benoit <calculus@rezozer.net>
   fpylll (U)

Jochen Sprickerhof <jspricke@debian.org>
   python-pcl (U)

Jonas Smedegaard <dr@jones.dk>
   python-av

Joost van Baal-Ilić <joostvb@debian.org>
   pyreadstat

Josue Ortega <josue@debian.org>
   python-rtmidi

Julien Puydt <jpuydt@debian.org>
   fpylll (U)
   pplpy (U)

Kevin Murray <kdmfoss@gmail.com>
   python-skbio (U)

Kunal Mehta <legoktm@debian.org>
   python-libzim

Leo Singer <leo.singer@ligo.org>
   healpy (U)

Liubov Chuprikova <chuprikovalv@gmail.com>
   cyvcf2 (U)

Luca Boccassi <bluca@debian.org>
   azure-uamqp-python (U)

Markus Koschany <apo@debian.org>
   pygame-sdl2 (U)

Matthias Klose <doko@debian.org>
   pygccjit

Michael Hanke <michael.hanke@gmail.com>
   pandas (U)
   statsmodels (U)

Michael Hanke <mih@debian.org>
   indexed-gzip (U)

Michael R. Crusoe <crusoe@debian.org>
   macs (U)
   python-pomegranate (U)

Mo Zhou <cdluminate@gmail.com>
   h5py (U)

Nikolaus Rath <Nikolaus@rath.org>
   python-llfuse

Nilesh Patra <nilesh@debian.org>
   python-cytoolz (U)

Ole Streicher <olebole@debian.org>
   montage (U)

Olivier Sallou <osallou@debian.org>
   python-thriftpy (U)

Paul Wise <pabs@debian.org>
   gensim (U)

Picca Frédéric-Emmanuel <picca@debian.org>
   opentsne (U)

Piotr Ożarowski <piotr@debian.org>
   uvloop

Rebecca N. Palmer <rebecca_palmer@zoho.com>
   libgpuarray (U)
   pandas (U)
   statsmodels (U)

Richard Ulrich <richi@paraeasy.ch>
   python-hidapi (U)

Roland Mas <lolando@debian.org>
   python-orderedset

Sandro Tosi <morph@debian.org>
   numpy

Sebastien Delafond <seb@debian.org>
   opentsne (U)

Stefano Rivera <stefanor@debian.org>
   pystemmer (U)

Steffen Moeller <moeller@debian.org>
   cyvcf2 (U)
   python-pomegranate (U)

Tobias Hansen <thansen@debian.org>
   cypari2 (U)
   pplpy (U)

Varun Hiremath <varun@debian.org>
   mayavi2 (U)

Vincent Cheng <vcheng@debian.org>
   kivy (U)

Vincent Prat <vivi@debian.org>
   pyregion (U)

Ximin Luo <infinity0@debian.org>
   cypari2 (U)
   fpylll (U)

Yao Wei (魏銘廷) <mwei@debian.org>
   python-openstep-plist (U)

Yaroslav Halchenko <debian@onerussian.com>
   indexed-gzip (U)
   pandas (U)
   statsmodels (U)

Yves-Alexis Perez <corsac@debian.org>
   libimobiledevice (U)

Étienne Mollier <emollier@debian.org>
   nipy (U)

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [next] | [standalone]

#15318

Hi debian-python (2023.11.25_16:23:46_+0000)
> As part of preparing for Python 3.12 in Debian, I've uploaded cython 3
> to experimental.
> 
> I did some test-building of reverse dependencies, and quite a lot of
> them fail.

I should have said, all the build logs are here:

https://people.debian.org/~stefanor/cython3/cython-3.0.5/

> Stefano Rivera <stefanor@debian.org>
>    pystemmer (U)

Fixed in 2.2.0.1-2

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#15319

Hi,

Le samedi 25 novembre 2023 à 16:23 +0000, Stefano Rivera a écrit :
> 
> Julien Puydt <jpuydt@debian.org>
>    fpylll (U)
>    pplpy (U)
> 

I had a look.

For fpylll: it has a newer upstream which works with more recent cython
versions, so I'm actually eager to see the move.

For pplpy, I'm a bit annoyed as I have no recollection of that
package... According to its homepage, the project has been archived, so
it's probably dead. But the sagemath package still depends on it (or at
least its d/control says it does) so we can't drop it yet.

Cheers,

JP

[toc] | [prev] | [next] | [standalone]

#15321

Hi,

Le samedi 25 novembre 2023 à 16:23 +0000, Stefano Rivera a écrit :
> 
> Julien Puydt <jpuydt@debian.org>
>    fpylll (U)
>    pplpy (U)


For pplpy, I found the package was pointing to an archived repo, but
the author had a newer one with a version which is supposed to be okay
(to be confirmed).

For fpylll, there is a newer version compatible with recent cython but
not with our current one. I'm discussing with upstream on how to have a
version compatible with both, but of course if cython 3 gets updated
the issue becomes moot.

Cheers,

J.Puydt

[toc] | [prev] | [next] | [standalone]

#15357

Le jeudi 30 novembre 2023 à 08:25 +0100, julien.puydt@gmail.com a
écrit :
> Hi,
> 
> Le samedi 25 novembre 2023 à 16:23 +0000, Stefano Rivera a écrit :
> > 
> > Julien Puydt <jpuydt@debian.org>
> >    fpylll (U)
> >    pplpy (U)
> 
> 
> For pplpy, I found the package was pointing to an archived repo, but
> the author had a newer one with a version which is supposed to be
> okay
> (to be confirmed).

I found the time to check: the last uploaded pplpy is good.

> For fpylll, there is a newer version compatible with recent cython
> but not with our current one. I'm discussing with upstream on how to
> have a version compatible with both, but of course if cython 3 gets
> updated the issue becomes moot.

The next fpylll will be ok ; and it's packaged in the git repo already
- it's just a 'dch -r', 'git tag -s' and 'dput' away.

Cheers,

J.Puydt

[toc] | [prev] | [next] | [standalone]

#15323

On Sat, Nov 25, 2023 at 04:23:46PM +0000, Stefano Rivera wrote:
> [...]
> So, that's 71 regressions with cython3. dd-list below. Please help us
> port to cython 3. If this isn't possible, Graham is preparing a
> cython-legacy package, to help the stragglers. But we're expecting that
> this won't have great Python 3.12 support...
> https://ftp-master.debian.org/new/cython-legacy_0.29.36-1~exp1.html

Indeed; there's already one Python 3.12 related bug in the legacy
version: it tries to import imp in pyximport.py.

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#15337

On Sat, Nov 25, 2023 at 04:23:46PM +0000, Stefano Rivera wrote:
> As part of preparing for Python 3.12 in Debian, I've uploaded cython 3
> to experimental.
> [...]
> 
> So, that's 71 regressions with cython3. dd-list below. Please help us
> port to cython 3. If this isn't possible, Graham is preparing a
> cython-legacy package, to help the stragglers. But we're expecting that
> this won't have great Python 3.12 support...
> https://ftp-master.debian.org/new/cython-legacy_0.29.36-1~exp1.html

I find that there's also a significant issue with relying on
cython3-legacy: it conflicts with cython3, meaning that it will be
impossible to simultaneously install packages depending on cython3 and
cython3-legacy.  Once cython 3.x moves from experimental to unstable
to testing and packages start depending on it, this will become a
significant issue.  I assume that the aim will be for everything to be
ported to cython 3.x and for cython3-legacy to be dropped from testing
before the trixie freeze?

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#15339

On Sun, Dec 10, 2023 at 08:12:40PM +0000, Julian Gilbey wrote:
> On Sat, Nov 25, 2023 at 04:23:46PM +0000, Stefano Rivera wrote:
> > As part of preparing for Python 3.12 in Debian, I've uploaded cython 3
> > to experimental.
> > [...]
> > 
> > So, that's 71 regressions with cython3. dd-list below. Please help us
> > port to cython 3. If this isn't possible, Graham is preparing a
> > cython-legacy package, to help the stragglers. But we're expecting that
> > this won't have great Python 3.12 support...
> > https://ftp-master.debian.org/new/cython-legacy_0.29.36-1~exp1.html
> 
> I find that there's also a significant issue with relying on
> cython3-legacy: it conflicts with cython3, meaning that it will be
> impossible to simultaneously install packages depending on cython3 and
> cython3-legacy.  Once cython 3.x moves from experimental to unstable
> to testing and packages start depending on it, this will become a
> significant issue.  I assume that the aim will be for everything to be
> ported to cython 3.x and for cython3-legacy to be dropped from testing
> before the trixie freeze?
I wonder how many packages actually need a runtime dep on cython. I
quickly checked three packages from `reverse-depends cython3` and while
python3-pysph probably uses cython to generate code at the run time (not
sure), python3-pyzoltan seems to only use it at the build time and
python3-epimodels doesn't seem to use it at all.

[toc] | [prev] | [next] | [standalone]

#15340

On Sun, Dec 10, 2023 at 09:30:03PM +0100, Andrey Rakhmatullin wrote:
> > I find that there's also a significant issue with relying on
> > cython3-legacy: it conflicts with cython3, meaning that it will be
> > impossible to simultaneously install packages depending on cython3 and
> > cython3-legacy.  Once cython 3.x moves from experimental to unstable
> > to testing and packages start depending on it, this will become a
> > significant issue.  I assume that the aim will be for everything to be
> > ported to cython 3.x and for cython3-legacy to be dropped from testing
> > before the trixie freeze?
> I wonder how many packages actually need a runtime dep on cython. I
> quickly checked three packages from `reverse-depends cython3` and while
> python3-pysph probably uses cython to generate code at the run time (not
> sure), python3-pyzoltan seems to only use it at the build time and
> python3-epimodels doesn't seem to use it at all.
(I may be terribly wrong, I just thought cython is almost always a build
time only dep and there are around 30 packages depending on it which was
surprising)

[toc] | [prev] | [next] | [standalone]

#15343

On 10.12.23 21:32, Andrey Rakhmatullin wrote:
> On Sun, Dec 10, 2023 at 09:30:03PM +0100, Andrey Rakhmatullin wrote:
>>> I find that there's also a significant issue with relying on
>>> cython3-legacy: it conflicts with cython3, meaning that it will be
>>> impossible to simultaneously install packages depending on cython3 and
>>> cython3-legacy.  Once cython 3.x moves from experimental to unstable
>>> to testing and packages start depending on it, this will become a
>>> significant issue.  I assume that the aim will be for everything to be
>>> ported to cython 3.x and for cython3-legacy to be dropped from testing
>>> before the trixie freeze?
>> I wonder how many packages actually need a runtime dep on cython. I
>> quickly checked three packages from `reverse-depends cython3` and while
>> python3-pysph probably uses cython to generate code at the run time (not
>> sure), python3-pyzoltan seems to only use it at the build time and
>> python3-epimodels doesn't seem to use it at all.
> (I may be terribly wrong, I just thought cython is almost always a build
> time only dep and there are around 30 packages depending on it which was
> surprising)
> 

yes, many setup.py's list that under install_requires. I hope we now 
identified most of them, and fixed these.  At least we were now able to 
do all the binNMUs.

You could package a non-conflicting cython-legacy, however that would 
require more changes, also how to build it.

Matthias

[toc] | [prev] | [next] | [standalone]

#15345

On 11.12.23 08:09, Matthias Klose wrote:
> On 10.12.23 21:32, Andrey Rakhmatullin wrote:
>> On Sun, Dec 10, 2023 at 09:30:03PM +0100, Andrey Rakhmatullin wrote:
>>>> I find that there's also a significant issue with relying on
>>>> cython3-legacy: it conflicts with cython3, meaning that it will be
>>>> impossible to simultaneously install packages depending on cython3 and
>>>> cython3-legacy.  Once cython 3.x moves from experimental to unstable
>>>> to testing and packages start depending on it, this will become a
>>>> significant issue.  I assume that the aim will be for everything to be
>>>> ported to cython 3.x and for cython3-legacy to be dropped from testing
>>>> before the trixie freeze?
>>> I wonder how many packages actually need a runtime dep on cython. I
>>> quickly checked three packages from `reverse-depends cython3` and while
>>> python3-pysph probably uses cython to generate code at the run time (not
>>> sure), python3-pyzoltan seems to only use it at the build time and
>>> python3-epimodels doesn't seem to use it at all.
>> (I may be terribly wrong, I just thought cython is almost always a build
>> time only dep and there are around 30 packages depending on it which was
>> surprising)
>>
> 
> yes, many setup.py's list that under install_requires. I hope we now 
> identified most of them, and fixed these.  At least we were now able to 
> do all the binNMUs.
> 
> You could package a non-conflicting cython-legacy, however that would 
> require more changes, also how to build it.

Graham created a tracker for these, and I filed bug reports:

https://release.debian.org/transitions/html/cython-runtime.html
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=cython-rt-dep&users=debian-python@lists.debian.org

[toc] | [prev] | [next] | [standalone]

#15347

On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> [...]
> > > > I find that there's also a significant issue with relying on
> > > > cython3-legacy: it conflicts with cython3, meaning that it will be
> > > > impossible to simultaneously install packages depending on cython3 and
> > > > cython3-legacy.  Once cython 3.x moves from experimental to unstable
> > > > to testing and packages start depending on it, this will become a
> > > > significant issue.  I assume that the aim will be for everything to be
> > > > ported to cython 3.x and for cython3-legacy to be dropped from testing
> > > > before the trixie freeze?
> [...]
> You could package a non-conflicting cython-legacy, however that would
> require more changes, also how to build it.

I had a very quick look at the packaged cython3-legacy.  One could
change the name of the module to Cython_legacy or probably better,
Cython0, and cython.py to cython0.py, pyximport to pyximport0.  Just a
handful of changes would be needed, I'm guessing.  Then it would be
co-installable with Cython 3.x, and any packages that actually need
cython3-legacy rather than Cython 3.x would have to be patched to call
the legacy version.  It's probably easier to just patch them for
Cython 3.x ;-)

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#15348

On 11.12.23 16:19, Julian Gilbey wrote:
> On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
>> [...]
>> You could package a non-conflicting cython-legacy, however that would
>> require more changes, also how to build it.
> 
> Hi Matthias,
> 
> Unfortunately, at least some of cython3-legacy doesn't currently work
> with Python 3.12, and is the primary cause of (at least) #1056531.
> cython3 provides the pyximport module, and that uses the imp module
> which has been removed from Python 3.12.
> 
> Two possible ways forward on this particular bug:
> 
> - Disable all of the cython tests for this package for the time being,
>    until cython 3.x migrates to testing - this is simple and effective.
> 
> - Patch cython3-legacy to use importlib rather than imp.  This is
>    probably a good thing to do anyway.  (It may also be good to do this
>    with cython3 version 0.x currently in testing/unstable until cython
>    3.x is able to be uploaded to unstable.)  Then have my package's
>    autopkgtest depend on cython3-legacy (unless cython3 0.x is also
>    patched).

I won't working on this. Have you tried to depend on the 
python3-zombie-imp instead?

[toc] | [prev] | [next] | [standalone]

#15351

On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
> On 11.12.23 16:19, Julian Gilbey wrote:
> > On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
> > > [...]
> > > You could package a non-conflicting cython-legacy, however that would
> > > require more changes, also how to build it.
> > 
> > Hi Matthias,
> > 
> > Unfortunately, at least some of cython3-legacy doesn't currently work
> > with Python 3.12, and is the primary cause of (at least) #1056531.
> > cython3 provides the pyximport module, and that uses the imp module
> > which has been removed from Python 3.12.
> > 
> > Two possible ways forward on this particular bug:
> > 
> > - Disable all of the cython tests for this package for the time being,
> >    until cython 3.x migrates to testing - this is simple and effective.
> > 
> > - Patch cython3-legacy to use importlib rather than imp.  This is
> >    probably a good thing to do anyway.  (It may also be good to do this
> >    with cython3 version 0.x currently in testing/unstable until cython
> >    3.x is able to be uploaded to unstable.)  Then have my package's
> >    autopkgtest depend on cython3-legacy (unless cython3 0.x is also
> >    patched).
> 
> I won't working on this. Have you tried to depend on the python3-zombie-imp
> instead?

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?

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#15352

On 11.12.23 19:55, Julian Gilbey wrote:
> On Mon, Dec 11, 2023 at 04:34:17PM +0100, Matthias Klose wrote:
>> On 11.12.23 16:19, Julian Gilbey wrote:
>>> On Mon, Dec 11, 2023 at 08:09:31AM +0100, Matthias Klose wrote:
>>>> [...]
>>>> You could package a non-conflicting cython-legacy, however that would
>>>> require more changes, also how to build it.
>>>
>>> Hi Matthias,
>>>
>>> Unfortunately, at least some of cython3-legacy doesn't currently work
>>> with Python 3.12, and is the primary cause of (at least) #1056531.
>>> cython3 provides the pyximport module, and that uses the imp module
>>> which has been removed from Python 3.12.
>>>
>>> Two possible ways forward on this particular bug:
>>>
>>> - Disable all of the cython tests for this package for the time being,
>>>     until cython 3.x migrates to testing - this is simple and effective.
>>>
>>> - Patch cython3-legacy to use importlib rather than imp.  This is
>>>     probably a good thing to do anyway.  (It may also be good to do this
>>>     with cython3 version 0.x currently in testing/unstable until cython
>>>     3.x is able to be uploaded to unstable.)  Then have my package's
>>>     autopkgtest depend on cython3-legacy (unless cython3 0.x is also
>>>     patched).
>>
>> I won't working on this. Have you tried to depend on the python3-zombie-imp
>> instead?
> 
> 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?

[toc] | [prev] | [next] | [standalone]

#15358

On Sat, Nov 25, 2023 at 04:23:46PM +0000, Stefano Rivera wrote:
> As part of preparing for Python 3.12 in Debian, I've uploaded cython 3
> to experimental.
> [...]
> 
> So, that's 71 regressions with cython3. dd-list below. Please help us
> port to cython 3. If this isn't possible, Graham is preparing a
> cython-legacy package, to help the stragglers. But we're expecting that
> this won't have great Python 3.12 support...
> https://ftp-master.debian.org/new/cython-legacy_0.29.36-1~exp1.html

Here's an update on cython-legacy.  I just tried running autopkgtest
on cython-legacy with Python 3.12, and unfortunately it fails.  I
can't quite work out how many tests fail (I don't understand the
format of the test output), but there are 25 lines containing the
string "FAIL" in the output of autopkgtest with the latest version of
cython-legacy (0.29.36-2, uploaded today).

We could just skip these tests - some of them are probably harmless -
but they probably indicate incompatibilty (unsurprisingly) with Python
3.12, though some of these incompatibilties may be restricted to the
tests themselves rather than the underlying Cython 0.x code.

I'd be happy to try uploading a version with these tests skipped - I
just wanted to check here first what the thoughts on this are.  (Note
that it is much better to modify other packages to work with Cython
3.x!)

Best wishes,

   Julian

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web