Hi, On Fri, Dec 02, 2016 at 03:50:07AM -0800, Emmanuel Charpentier wrote: [...] > As far as I can tell, everybody else will have someday to hit the network > (at least for PIP packages...).
It is not always possible. At least many users of Sage Debian Live from places where there is not (much) network should not be dependent of internet connection, not only in remote areas (which was the use case for the creation of SDL): it has also been required during various workshops, where this was necessary e.g. when the wifi does not allow guests to be connected. We should still be able to propose a self-contained software (while at the same time let the possibility to use distro's deps). Regarding source tarball, it might (?) be a good idea to ship an extended tarball with all optional and pip packages (e.g. by letting pip to look into the upstream/ directory before going to PyPI). BTW, it is pretty important that Sage only connects to the internet when explicitely asked by the user (e.g. when using oeis). Currently, pip is leaking when used, just to check latest version, it is pretty annoying. The use of a remote three.js CDN is also problematic with that respect. Ciao, Thierry -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
