On Monday, September 1, 2025 at 11:18:36 PM UTC-5 Dima Pasechnik wrote:
symlinking is flaky across VMs and filesystems. E.g. if you run Jupyter in a Windows browser (or in VSCode), with Sage running in WSL, then it seems to me one cannot avoid "jupyter kernelspec install". Well, yes, it's about 2.3Gb of data, but with the current capacity and cost of SSDs it's not something to worry about. I think most of this statement is highly questionable. Symlinking either works or does not work within a given context. If there were an example showing that it fails in this situation then that would be something to worry about. If not, then talk about "flakiness" is just talk. Also, 2.3GB is almost twice the size of the entire sage AppImage and is larger than the maximum size allowed for a release download in GitHub. The sage AppImage weighs in at 1.25GB, and occupies 1.25 GB on the user's disk, even though it contains the complete English documentation for sage. The way this works in the AppImage is that the html files stored in the AppImage are gzipped. The English documentation shrinks to only 120MB when redundant files are removed and the rest are gzipped. All browsers are able to decompress gzipped html files on the fly with no noticeable performance lag. So the AppImage provides its own webserver which delivers gzipped files when the reference() command or the jupyter notebook "Help" menu are used to view documentation. Claiming that 2.3GB (or 10GB in the case of a full build of Sage) is not something to worry about is pretty crazy, even if there do exist some contexts where it is not an issue. There are other contexts where it is a serious issue. - 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/6d8a678e-7b28-4d25-9c31-7a55f6596dd1n%40googlegroups.com.
