On 16 May 2018 at 22:15, Jeroen Demeyer <j.deme...@ugent.be> wrote: > On 2018-05-16 17:26, Erik Bray wrote: > >> I'm not sure, but I think this might be pip-related. I think Jeroen >> mentioned something about this to me a couple weeks ago. Is it >> possible you upgraded the pip in your Sage install? >> > > Indeed, I guess you are using pip 10 by accident. >
I think so. I killed that build, downgraded pip, and restarted make. Something was confused enough that I then just did "make distclean && make" and now all is well. > > It might be a good idea to upgrade the pip in Sage and fix this issue. I myself have no idea what the implications of that might be! John > > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
