Re: [petsc-dev] futurize

2018-04-02 Thread Jed Brown
Lisandro Dalcin writes: > On 2 April 2018 at 23:08, Jed Brown wrote: >> Would it be too disruptive to run futurize "stage 1" before the 3.9 >> release? > > Would this introduce any dependency outside plain Python 2 stdlib? No. These are the only new imports. +from functools import reduce +fro

Re: [petsc-dev] futurize

2018-04-02 Thread Lisandro Dalcin
On 2 April 2018 at 23:08, Jed Brown wrote: > Would it be too disruptive to run futurize "stage 1" before the 3.9 > release? Would this introduce any dependency outside plain Python 2 stdlib? Sorry, I'm not an expert in these futurize/modernize/six/whatever stuff, I got used to write Py 2/3 compat

[petsc-dev] futurize

2018-04-02 Thread Jed Brown
Would it be too disruptive to run futurize "stage 1" before the 3.9 release? The source would remain Python-2 only, but would be "modernized" so that the next stage (supporting Python-3) would be less disruptive. The goal here would be to make it easier to port configuration changes from 'maint'