Hi Thierry, On 2016-04-16, Thierry <sage-googlesu...@lma.metelu.net> wrote: > - for standard packages, the source must be provided since the tarball is > supposed to be autonomous.
If I understand correctly, that'S exactly what the proposal would change: Sage sources would contain the information that package "foo" has to be pip-installed by default, but it does *not* provide foo's source tar-ball, since that's not needed in order to pip-install it. I suppose there could be a file in the Sage sources providing a list of everything that should be pip-installed by default, and then as soon as Sage has built its own version of Python, it would go through that list and install stuff. And that's a kind of modularisation that I'd like. Best regards, Simon -- 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.
