Re: [scikit-image] Python 3, revisited

2017-07-11 Thread Juan Nunez-Iglesias
Yes Matthew, that is exactly my issue with that line (and many other linear algebra-heavy parts of skimage). On 11 Jul 2017, 6:43 PM +1000, Matthew Brett , wrote: > Hi, > > Certainly no need to duck, from my point view - but for this: > > On Tue, Jul 11, 2017 at 3:07 AM, Juan Nunez-Iglesias > > B

Re: [scikit-image] Python 3, revisited

2017-07-11 Thread Matthew Brett
Hi, Certainly no need to duck, from my point view - but for this: On Tue, Jul 11, 2017 at 3:07 AM, Juan Nunez-Iglesias > Beautiful linalg syntax ruined by using Python 2.7 > https://github.com/scikit-image/scikit-image/pull/2394#discussion_r94191032 - do you mean differences like: D1 = np.vstac

Re: [scikit-image] Python 3, revisited

2017-07-11 Thread Juan Nunez-Iglesias
Oh and thanks Tom, adding Matplotlib to the list of Python 3-only libs will be a massive boost! On 11 Jul 2017, 2:48 PM +1000, Stefan van der Walt , wrote: > 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 l

Re: [scikit-image] Python 3, revisited

2017-07-11 Thread Juan Nunez-Iglesias
Thanks for the input, Matt! Yes, if you look at our original discussion, my idea would be to continue to do bug-fix releases on the 0.14 branch for some time, but only provide new features on the Python 3 master. On 11 Jul 2017, 2:48 PM +1000, Stefan van der Walt , wrote: > Hi Juan > > On Mon,

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

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 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

[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