Hi Nilson sorry -- I was not following cython package recently so all kudos to Stefano and other team members for taking good care of it under team maintainership.
I think the best would have been to check existing bug reports and follow up on them, thus to minimize traffic I immediately CCing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028157 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", in git log for scipy upstream I find last record for cython3 compat from v1.5.0rc1~75 in 2020! So scipy was in sync with cython development - for debian package upper bound was introduced in https://salsa.debian.org/python-team/packages/scipy/-/commit/7a469e2435a01468b769f11c14f7e2a5c318fe4a but no detailed reason provided. so might have been general precaution. 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? -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik
