I know what you mean and cannot disagree. What I would like to understand is why it happens all of a sudden. The python upgrade is probably a false lead. The only patch added doesn't touch that part of the build process at all. There must be something else.
Steve, what was built before python following the checkout of the upgrade according to sage's build log? François On Friday, February 28, 2014 10:43:47 PM UTC+13, Volker Braun wrote: > > It is a Sage bug if we call a Python program while Python is half-built > and not working imho. > > On Thursday, February 27, 2014 11:46:48 PM UTC+1, François wrote: >> >> That may be actually the beginning of an explanation of why the problem >> is solved by upgrading system mercurial - the new one uses a newer python >> infrastructure in Gentoo and may be protected from such injection. >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
