On Tuesday, September 2, 2025 at 9:19:40 AM UTC-5 Dima Pasechnik wrote:
OK, so the 2.3Gb issue goes away if we compress and prune the docs, and only only then do jupyter kernelspecs install Is this what you are saying (because 120Mb is really not something to worry about) ? Yes. By the way, Sage has custom code in the SageKernel class which makes the docs available from the Help menu in a jupyter notebook. It does not handle the gzipped files, so we modify it. For that we use the cocoserver pypi package. I don't know where 10Gb come from - pdf docs? Docs for all the optional and standard packages? % du -sch sage 11G sage 11G total That is the image we use as a starting point for both Sage_macOS and sage_appimage. It includes many optional packages as well as the html documentation in all languages and the huge amount of detritus left over after a build (which we remove). It does not include pdf docs. So 10GB (well, really 11GB) is just the disk footprint of a normal Sage installation when Sage is built from source. - Marc -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-release/0025836f-ebfa-444c-85a8-6f89fb11b819n%40googlegroups.com.
