Currently all "standard" packages of the Sage distribution, by policy (https://doc.sagemath.org/html/en/developer/packaging.html; recommended reading), - either can be installed from source ("normal" packages); - or they are Python packages that can be installed from platform-independent wheels.
(We added the second option in order to treat Javascript assets as prebuilt data, thus avoiding the complexity of Javascript build infrastructure in the Sage distribution.) In https://github.com/sagemath/sage/pull/38219 (needs review), I propose the following mild policy change: - as a third option, a "standard" package is allowed to be a Python package that can be installed from platform-dependent (binary) wheels. In this case, a "configure" option must be provided that disables the package. (Again this new option is motivated by avoiding the complexity of new build infrastructure related to another language; in this case, Rust. See the PR for two example Rust-based example packages; previous discussion: https://groups.google.com/g/sage-devel/c/JiSryImYGe0/m/4B8z6F4AEwAJ) -- 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/57f1ca35-2b31-4cb5-b106-c19cfa2bd804n%40googlegroups.com.
