This sounds like a good plan to me. This means that Python 2 is still supported and up to date for at least another year with scikit-image, but internally we can already start taking advantage of Python 3 features. Also, I have the feeling that there is already relatively good Python 3 support in the scientific community at this point. It will only get better in another year when we release 0.15.
On Nov 11, 2017, at 7:33 AM, Stefan van der Walt email@example.com wrote:
I'd like to make a 4th attempt to determine our transition pathway to Python 3. The last thread is here:
I would like to propose that the next version, 0.14 (scheduled for March of next year), becomes the last targeted for Python 2. It will also be an LTS (Long Time Support), which means we will backport serious fixes for a period of one year. 0.15 will then target Python >= 3.5 only (sorry, no f-strings yet!).
Let me know your thoughts.
Stéfan _______________________________________________ scikit-image mailing list firstname.lastname@example.org https://mail.python.org/mailman/listinfo/scikit-image
The thread split off into another, but I am continuing the discussion here.
It looks like we have general support for the notion to do one more Python 2.7 release, and to then switch to Python >= 3.5.
Stefan, Has the schedule been changed? I remember we were planning to release 0.14 in November 2017 (see https://mail.python.org/pipermail/scikit-image/2017-September/005352.html).
As far as I recall, Egor volunteered to be release manager---thank you! I think we can hold off a bit on 0.14: our last release was in September, and there are a few PRs in the pipeline near completion. How about we split off the 0.14.x branch beginning of February?
Since we're going to be backporting a lot of patches, should I ask Matthias Bussonier to activate