On Sunday, May 28, 2023 at 10:01:41 AM UTC-7 Tobias Diez wrote: I can also point at the already existing possibility to use Conda's Python packages on a Conda-based install.
This mode of installation ( https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-all-dependencies-for-the-sage-library-experimental) bypasses the Sage distribution entirely and installs the Sage library separately using pip. And there were problems with this mode of installation for Python 3.8 that no one had the time to fix. On the other hand, it works perfectly well and is tested via github actions for all NEP29-supported Python versions. So this serves as a prime example of how supporting multiple Python versions can be challenging. What you are describing is a downstream distribution problem, not a Sage problem. It is not under control of our project what conda packages are available and working for what Python version. It does point to an important issue: That if we abandon the Sage distribution in favor of using conda-forge as our reference environment --- as recently discussed as a possibility --- then we are losing control of the necessary software environment for running tests. So if we go this way, we need to find a way to motivate Sage developers to engage in matters of conda-forge packaging. -- 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/9769333e-61ca-4ee4-a6aa-dcdba7b1dbb3n%40googlegroups.com.
