On 2023-08-10 22:18, Yaroslav Halchenko wrote:
Hi Nilson
...
Please follow up here and state your interest to see 3.0.0 in debian.
Note https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028157#10
The latest version of scipy, 1.11.1, needs Cython>=0.29.35
but also declares Cython<3.0.
So we need first check with scipy on either it is ready for cython
3:
- upstream has (and I don't think ever had) no upper bound
> grep Cython pyproject.toml
"Cython>=0.29.18",
...
CCing Drew Parsons maintaining scipy -- may be he could recall the need
for upper bound or just make a verdict to drop that upper bound?
The upper bound for scipy is declared in its pyproject.toml, but you're
right it's not declared so in scipy git.
They often add an upper bound in the release tarballs. I think it's a
mechanism so keep released code more manageable, avoiding unanticipated
problems with future versions.
But since the upper bound is not in the main branch in git, that's clue
that it might not be a real upper bound.
On the other hand some problems with cython 3 were reported,
https://github.com/scipy/scipy/issues/18909
but already fixed in
https://github.com/scipy/scipy/pull/18242
(merged commit a181fd5 into scipy:main on May 3)
The patch is already in scipy 1.11.1, but we can't test it because of
doit (Bug#1042459). If you can push the doit maintainers along that
would be helpful. doit should probably be moved to the Debian Python
Team.
But in any case PR18242 looks simple enough to backport to scipy 1.10.1
. Would need to be tested first. Get cython3 into experimental so we can
check.
Drew
