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
