On Tue, Aug 11, 2015 at 7:44 AM, William Stein <wst...@gmail.com> wrote: > On Tue, Aug 11, 2015 at 1:15 AM, Volker Braun <vbraun.n...@gmail.com> wrote: >> [Top-posted to stop threadjacking the SymEngine post] > > I'm sorry for doing that -- it was sort of relevant to his question, > but starting a new thread is much better. > >> >> Just have the sage-python-library install using pip, assuming your system >> has all the dependencies, is almost trivial. The real question is always how >> to handle the dependencies, starting at a Fortran compiler. Also, just to >> establish a baseline for discussion, Daniel Holth (pip author) said: "When >> people ask whether wheel can be used to distribute any other kind of >> software or dependency (libsdl, libqt, etc.) I recommend they take a look at >> system packaging tools or conda" (comment at >> http://continuum.io/blog/conda_packaging). >> >> So IMHO the right solution is to first separate all the C/C++-level >> dependencies (gcc, pari, python itself,...) from the Python libraries. We >> still need a way to have a "canonical" stack of the C/C++ dependencies to >> test against and patch if necessary, but you could switch that for OS >> packages (if there is such a thing on your platform). There are various ways >> to do this, hashdist being one of them, and we can likely share at least >> some of the package maintenance effort with others. > > +1 -- this makes good sense.
I like this. I was going to ask about it, because SymEngine depends on CMake, and that's not very practical to build using pip. Also, we are discussing to split the symengine C++ library and its Python wrappers into separate packages (so that the Python wrappers can be installed against multiple Python versions at once, if needed, and also so that other wrappers like Julia/Ruby can reuse the same C++ library --- it can be done already, but it's cleaner if it is separate). The C++ package can be installed using cmake and would be part of the C/C++ level dependencies. The Python wrappers would be installed using pip, and those would be tightly integrated with SymPy and Sage. That seems to be aligned with what Volker proposed. Let me know. Ondrej > >> Then sage-the-python-library could just install itself and its Python >> dependencies with pip and requirements.txt > > That would be awesome. > >> >> >> -- >> 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 http://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. > > > > -- > William (http://wstein.org) > > -- > 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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
