Ahem... There are two components to consider : - the package by itself
- its interface to Sagemath. Case in point : the Mathematica interface, which is standard (*i. e.* installed in all cases), but active if and only if Mathematica (or the Wolfram engine) is present in the target system. This distinction has not been made in the case of R. I do not know if `rpy2` can be installed in a system not having R. A possible solution could mimin the mathematica interface, which raises an exception when called on an system without a mathematica engine installed : it prints an inforrmative message pointing to the possible solutions of the problem... HTH, Le samedi 25 mars 2023 à 21:44:31 UTC+1, Matthias Koeppe a écrit : > I've opened issue https://github.com/sagemath/sage/issues/35347 for this > > > On Saturday, March 25, 2023 at 1:40:19 PM UTC-7 Matthias Koeppe wrote: > >> On Saturday, March 25, 2023 at 12:52:00 PM UTC-7 Dima Pasechnik wrote: >> >> I propose to introduce the notion of semistandard package. >> >> >> "Semistandard" sounds good to me. >> >> We have a few more packages that are of this type: >> - sqlite is only installed if we build our own copy of python3 >> - openssl is only installed if we build our own copy of python3 or curl >> >> And some packages can probably be promoted from "optional" to >> "semistandard". >> - jupymake - should probably be installed when a system polymake is found >> - more to come as part of the modularization. >> >> >> > -- 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/9e8df3f3-9cd3-4818-8760-9d072bb295cdn%40googlegroups.com.
