On Mon, 2024-10-07 at 07:55 -0700, William Stein wrote: > Hi, > > There are a number of big chunks of functionality in Sage, like interval > arithmetic (I was just going to say this and Marc beat me to it), and the > sage preparser, which could be valuable as separate packages that Sage uses. > > License of Sage is GPLv3, whereas the vast majority of the scientific > Python (etc.) ecosystem is BSD/MIT/Apache/etc (e.g., sympy: > https://www.sympy.org/en/index.html). Thus most of the broader Python > ecosystem won't touch any Sage packages with a 10 foot pole, even if they > are useful and better than what is available. For example, many would > select sympy over a similar part of sage, just because of the license. I > don't think there is anything to be done about this. It's just something > to be aware of, which will forever significantly limit the impact of Sage > on the broader Python ecosystem.
You didn't say that it does, just that they think it does, but... how would Sage being GPLv3 affect these people in any way? The GPLv3 is nearly irrelevant for end users. It only stops you from doing pathological things like modifying the source code, compiling the result, shipping the binaries, and then refusing to publish the source code to those binaries. Adding a sage-* package to your dependencies in pyproject.toml does not even constitute distribution. -- 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/a7e73053f605427829f8158a53513433b7ca8def.camel%40orlitzky.com.
