Since trac #28426 (merged pretty recently), when building with Python 3, we do not build Python 2. Before that, we always built both.
On Sunday, November 3, 2019 at 12:57:02 PM UTC-8, Dima Pasechnik wrote: > > I am surprised we still even build python2 by default. Isn't it an > optional package? > > On Sun, 3 Nov 2019, 20:52 Simon King, <simo...@uni-jena.de <javascript:>> > wrote: > >> Hi Dima, >> >> On 2019-11-02, Dima Pasechnik <dim...@gmail.com <javascript:>> wrote: >> > There "python" is Sage's Python, "pip" manages its modules, etc. >> >> IIRC, that's not true for Sage's py-3 version. Namely, if one opens a >> sage-with-py-3 shell, then "python" still means "python2". So, if you >> really want Sage-with-py-3's Python installation, you should either do >> "sage -python" or (in a Sage shell) "python3". And I think the same >> holds for pip. >> >> Best regards, >> Simon >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-s...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-support/qpnel6%24itu%241%40blaine.gmane.org >> . >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/45d0a564-549e-4fea-addf-dc2e30cc4001%40googlegroups.com.