[petsc-dev] python3 migration [of configure]

[Satish Balay]

We've already commited to python-2.6

https://bitbucket.org/petsc/petsc/commits/db5c7c58aec

I got the impression [by reading the urls below] - that we would have
to commit to python-2.7 to get configure working with both python2 and
python3.

Satish

On Wed, 21 Feb 2018, Jed Brown wrote:

> I've tried running futurize and python-modernize on BuildSystem.
> Futurize appears to be better supported and produces code that does not
> depend on the "six" module.  The changes are pretty cosmetic and
> sensible.  There are only a couple files that import "from future" -- if
> we removed that dependency manually then I think configure would work
> with base Python (no installed libraries).  This requires committing to
> python-2.6 minimum.  I think we should do it now in 'master'.
> 
> Satish Balay <balay at mcs.anl.gov> writes:
> 
> > Jed probably has a plan for this. The info at this link appears useful.
> >
> > https://lwn.net/Articles/747654
> > https://fosdem.org/2018/schedule/event/python3/
> >
> > Noteable:
> > "Python 2.7 support was extended from 2015 to 2020"
> >
> > Satish
>