[scikit-image] Python 3, revisited

2017-07-10 Thread Juan Nunez-Iglesias
Hi everyone, I’d like to revisit the Python 2 deprecation issue. Since the last discussion, IPython has gone Python 3-only, and Astropy just announced their 2.0 release as being the last one to support Python 2, with 3.0, scheduled in six months, out in 6 months. I’ve been obsessively catalogu

Re: [scikit-image] Python 3, revisited

2017-07-10 Thread Matt Craig
Hi, Astropy dev here -- just to clarify a little bit, bug fixes will be backported to the 2.0 release for two years, so until June 2019. Very much looking forward to 3.0 in 6 months though! Matt On Mon, Jul 10, 2017 at 9:07 PM, Juan Nunez-Iglesias wrote: > Hi everyone, > > I’d like to revisi

Re: [scikit-image] Python 3, revisited

2017-07-10 Thread Thomas Caswell
It is on the Matplotlib roadmap to have a python3 only release targeted for SciPy 2018 as well. Python 3.7 is scheduled for June 2018 ( https://www.python.org/dev/peps/pep-0537/) so targeting {3.6, 3.7} as the supported versions of python (which at that point should be the two most recent) is not

Re: [scikit-image] Python 3, revisited

2017-07-10 Thread Stefan van der Walt
Hi Juan On Mon, Jul 10, 2017, at 19:07, Juan Nunez-Iglesias wrote: > I’d like to revisit the Python 2 deprecation issue. Since the last > discussion, IPython has gone Python 3-only, and Astropy just announced[1] > their 2.0 release as being the last one to support Python 2, with 3.0, > schedule