<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=""><div class=""><blockquote type="cite" class="">They won't have /usr/bin/python unless they explicitly install<br class="">python-is-python3. Since no packages should depend on<br class="">python-is-python3, only Python users who work with unpackaged software<br class="">(Python developers and developer-adjacents) *and* learn about it will<br class="">have it. It means PETSc should work with systems that don't have python<br class="">in their path.<br class=""></blockquote></div><div class=""><br class=""></div>Perhaps adopting valgrinds model might be more appropriate in that case?<div class=""><br class=""></div><div class="">They require you run autogen.sh (which I don’t know that we need), and then configure which runs in shell and does the configure. We don’t necessarily have to do all of our configure in shell, just find a suitable python and call configure_in_python.py. I don’t know how they get around not having to chmod+x the shell scripts however, maybe because configure.sh has the shebang (!# /usr/bin/env sh) in it already?</div><div class=""><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<br class="">Cell: (312) 694-3391</div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Apr 18, 2020, at 1:15 PM, Jed Brown <<a href="mailto:jed@jedbrown.org" class="">jed@jedbrown.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Satish Balay <<a href="mailto:balay@mcs.anl.gov" class="">balay@mcs.anl.gov</a>> writes:<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">From the page:<br class=""></blockquote><br class=""> make sure package doesn't call python at build- or compile time (as there won't be a python package and no python command in bullseye, only python3.)<br class=""></blockquote><br class="">Sure this makes sense for building distro packages - so that they have correct dependencies.<br class=""><br class="">But its not indicative of user install not having /usr/bin/python.<br class=""></blockquote><br class="">They won't have /usr/bin/python unless they explicitly install<br class="">python-is-python3. Since no packages should depend on<br class="">python-is-python3, only Python users who work with unpackaged software<br class="">(Python developers and developer-adjacents) *and* learn about it will<br class="">have it. It means PETSc should work with systems that don't have python<br class="">in their path.<br class=""></div></div></blockquote></div><br class=""></div></body></html>