On Friday, September 24, 2021 at 4:23:32 AM UTC-7 Dima Pasechnik wrote: > > On Fri, 24 Sep 2021, 02:12 Matthias Koeppe, <matthia...@gmail.com> wrote: > >> I repeat my strong objections to the proposed change -- which does not >> solve any problems and only creates new ones. >> 7. (As I explained before in >> https://trac.sagemath.org/ticket/32532#comment:11) in particular, Python >> users / developers generally have a working gcc (because many Python >> packages include extension modules that need to be compiled) but they have >> no need to have gfortran installed. The reason is that the few Python >> packages that use gfortran (such as scipy) have high-quality deployments of >> wheels to PyPI, which are widely used. Sage, however, does not yet have a >> working strategy that would enable us to use wheels from PyPI. As you know, >> I have been working on a PyPI-based deployment solution for Sage in >> https://trac.sagemath.org/ticket/29039; this builds everything from >> source. >> > > Why does it build everything from source? E.g. numpy doesn't build Fortran > compilers. > Why do we have to outdo other Python projects here? >
I have explained in the paragraph that you quoted (and previously in #32532). Wheels. They have wheels. We don't. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/bffb95ab-3407-487f-8e19-b8945f7e10c3n%40googlegroups.com.
