[petsc-users] Python version needed for internal scripts

[Nicolas Barral]

Thanks Matt, Pierre, Lisandro and Jed for your help.

Does the python version chosen to call the configure script impact other 
petsc scripts ?

For now keeping python as an alias for python2 seems safer (until proven 
otherwise) due to other codes.

@Pierre: I meant the search button in https://lists.mcs.anl.gov/... 
wouldn't return anything, even on as obvious as queries as "petsc". It 
does work now, so not sure what happened.

Thanks,

-- 
Nicolas



On 14/10/2020 12:20, Matthew Knepley wrote:
> On Wed, Oct 14, 2020 at 6:01 AM Nicolas Barral 
> <nicolas.barral at math.u-bordeaux.fr 
> <mailto:nicolas.barral at math.u-bordeaux.fr>> wrote:
> 
>     Hi all,
> 
>     Apologies if the question has already been asked, but the ML archive
>     search seems to be broken (or has it never worked ?).
> 
>     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 ?
> 
>     '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.
> 
> 
> Right now, PETSc works with both Python2 and Python3. I am not sure how 
> long we can support Python2,
> but the aim is to support it until End of Life, probably on Red Hat 
> since they change the slowest I think.
> 
>    Thanks,
> 
>      Matt
> 
>     Thanks
> 
>     -- 
>     Nicolas
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their 
> experiments is infinitely more interesting than any results to which 
> their experiments lead.
> -- Norbert Wiener
> 
> https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>