<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello Nicolas,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 14 Oct 2020, at 12:00 PM, Nicolas Barral <<a href="mailto:nicolas.barral@math.u-bordeaux.fr" class="">nicolas.barral@math.u-bordeaux.fr</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all,<br class=""><br class="">Apologies if the question has already been asked, but the ML archive search seems to be broken (or has it never worked ?).<br class=""></div></div></blockquote><div><br class=""></div><div>What do you mean broken? Can’t you access this URL <a href="https://lists.mcs.anl.gov/pipermail/petsc-dev/" class="">https://lists.mcs.anl.gov/pipermail/petsc-dev/</a> ?</div><div>I know that some French ISP are getting blocked by the ANL firewall, but I don’t think I've ever had this issue with the ML.</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">Many petsc scripts require a 'python' executable, which python should that be ? For now, python3 seems to have worked with the configure scripts and petsc_gen_xdmf scripts, but can I safely assume it will always be the case ?<br class=""></div></div></blockquote><div><br class=""></div><div>This was discussed in great length in the ML when 3.13.5 (or was it 3.13.4?) was released (because it was kind of broken at first), see <a href="https://lists.mcs.anl.gov/mailman/htdig/petsc-dev/2020-April/025879.html" class="">https://lists.mcs.anl.gov/mailman/htdig/petsc-dev/2020-April/025879.html</a> + <a href="https://gitlab.com/petsc/petsc/-/merge_requests/2818" class="">https://gitlab.com/petsc/petsc/-/merge_requests/2818</a></div><div>This was then patched some more <a href="https://gitlab.com/petsc/petsc/-/merge_requests/2831" class="">https://gitlab.com/petsc/petsc/-/merge_requests/2831</a> because some Python versions are not shipping distutils.sysconfig which is mandatory for the configure to go through.</div><div><br class=""></div><div>I think you can assume that a correct Python version will be picked up for you by configure. If this is not the case, we will need to fix this (by adding another check?).</div><div><br class=""></div><div>Thanks,</div><div>Pierre</div><br class=""><blockquote type="cite" class=""><div class=""><div class="">'python' is usually an alias for python2, so making it point at python3 seems a bit dangerous. Yet, python2 was removed from recent Ubuntus and maybe others, and if I have no python2 installed, and no 'python' alias, I have to manually edit all the scripts.<br class=""><br class="">Thanks<br class=""><br class="">-- <br class="">Nicolas<br class=""></div></div></blockquote></div><br class=""></body></html>