@Kwankyu, replying here to your comments. The cython constraint in scipy is for build-time. Sagelib only cares about the fact that scipy is installed in the same venv, not how you install or build it. In fact, pip uses build isolation by default, or you may install scipy using the prebuilt wheel from pypi, or you use conda. In neither of these cases, would sagelib ever even see the cython used to build scipy. It's a sage-the-distro specific problem, since this distribution insists that you need to be able to compile sagelib with the same cython version as scipy.
Moreover, there is actually a very simple way to specify a different constraint for sage-the-distro: just remove the auto-gen of the version-requirements file, and provide an own one for sage-the-distro. On Sunday, August 25, 2024 at 11:38:17 AM UTC+2 dim...@gmail.com wrote: > No, it is Sage the distro getting in the way of sagelib. > On Sunday, August 25, 2024 at 6:52:40 AM UTC+1 Matthias Koeppe wrote: > >> On Friday, August 23, 2024 at 1:21:47 PM UTC-7 tobia...@gmx.de wrote: >> >> Why would one want to specify a more narrow version range? >> >> >> It's not a goal, it's a tradeoff. >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/7ed58515-fd26-46dd-905a-2e15a7914fc4n%40googlegroups.com.
