Satish Balay <ba...@mcs.anl.gov> writes: >> >From the page: >> >> 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.) > > Sure this makes sense for building distro packages - so that they have > correct dependencies. > > But its not indicative of user install not having /usr/bin/python.
They won't have /usr/bin/python unless they explicitly install python-is-python3. Since no packages should depend on python-is-python3, only Python users who work with unpackaged software (Python developers and developer-adjacents) *and* learn about it will have it. It means PETSc should work with systems that don't have python in their path.
