Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15347
| From | Julian Gilbey <julian@d-and-j.net> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: cython 3.x (for Python 3.12) |
| Date | 2023-12-11 11:30 +0100 |
| Message-ID | <HJLHX-cOE5-1@gated-at.bofh.it> (permalink) |
| References | <HE3Hz-8dHD-3@gated-at.bofh.it> <HJyrn-cGqF-7@gated-at.bofh.it> <HJyKJ-cGwP-1@gated-at.bofh.it> <HJyKJ-cGwP-5@gated-at.bofh.it> <HJIAp-cMER-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web