Presently we distribute a number of tarballs that are copies of pip-installable Python packages, which are dependencies of something, and maintain placeholders for them in build/pkg/ (this will be completely true as soon as #14840 is merged). This is a lot of unnecessary stuff to carry around, and is quite different to what is done in pythonic (as well as ocaml, haskell, Macaulay2, etc) universe.
My proposal is to get rid of these, and install pip-installable dependencies directly. Perhaps maintaining a catalog of such dependencies in some way; perhaps such facilities are provided by pip already, one needs to check this out. We may keep (some) placeholders in build/pkg, for the purpose of bootstrapping. One added advantage is that we can provide a sane way to install packages which cannot be installed from distributed sources, such as ssl support. In case one wants all the sources needed for a complete Sage install packaged locally, this is easy to achieve by providing a custom pip repo; such a repo may become some kind of optional component. -- 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.
