Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

Hi everyone, Just my two cents: I echo the sentiments mentioned earlier in this thread, and think that there is strong motivation to move away from 2.6 +1! Nelson Liu On Mon, Jan 11, 2016, 9:20 AM Andy wrote: > This seems like a good motivation. > I think we heard a lot of

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

This seems like a good motivation. I think we heard a lot of people not having any issues, and more people going this way. So let's go for it? [that is change the readme, change the build matrix, grep the source for backports] On 01/08/2016 08:55 AM, Olivier Grisel wrote: > Yet another

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

On Fri, Jan 8, 2016 at 5:55 AM, Olivier Grisel wrote: > Yet another perspective: > And yet another, in case it helps you make this decision. IPython's official statement on our website reads: IPython supports Python 2.7 and 3.3 or newer. Our older 1.x series supports

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

Yet another perspective: I am currently working with Thomas Moreau @tomMoral on more robust process management for joblib / multiprocessing and supporting Python 2.6 seems to be tedious to do correctly (we need to backport a lot of code from more recent versions of multiprocessing) and will

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

On Mon, Jan 4, 2016 at 9:41 PM, Andreas Mueller wrote: > > > On 01/04/2016 03:31 PM, Joel Nothman wrote: >> FWIW: features that I have had to remove include format strings with >> implicit arg numbers, set literals, dict comprehensions, perhaps >> ordered dicts / counters. We

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

On Mon, Jan 04, 2016 at 01:22:12PM -0500, Andreas Mueller wrote: > I'm not sure I'm for dropping 2.6 for the sake of dropping 2.6. I agree. I find the attitude of the post that I mentionned a bit annoying: dropping support for the sake of forcing people to move isn't a good thing. It should bring

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

I have many times committed coded and had to fix for python 2.6. FWIW: features that I have had to remove include format strings with implicit arg numbers, set literals, dict comprehensions, perhaps ordered dicts / counters. We are already clandestinely using argparse in benchmark code. Most of

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

On 01/04/2016 03:31 PM, Joel Nothman wrote: > FWIW: features that I have had to remove include format strings with > implicit arg numbers, set literals, dict comprehensions, perhaps > ordered dicts / counters. We are already clandestinely using argparse > in benchmark code. You probably just

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

For what it’s worth, pandas is dropping 3.3 in our next release (0.18 maybe end of this month). We’re possibly dropping 2.6 as well, but it might get one more release. -Tom > On Jan 4, 2016, at 7:28 AM, Gael Varoquaux > wrote: > > Happy new year everybody, >

[Scikit-learn-general] Dropping Python 2.6 compatibility

Happy new year everybody, As a new year resolution, I suggest that we drop Python 2.6 compatibility. For an argumentation in this favor, see http://www.snarky.ca/stop-using-python-2-6 (I don't buy everything there, but the core idea is there). For us, this will mean more usage of context

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

Subject: Re: [Scikit-learn-general] Dropping Python 2.6 compatibility For what it’s worth, pandas is dropping 3.3 in our next release (0.18 maybe end of this month). We’re possibly dropping 2.6 as well, but it might get one more release. -Tom > On Jan 4, 2016, at 7:28 AM, Gael Varoqu

Re: [Scikit-learn-general] Dropping Python 2.6 compatibility

Happy new year! I think it would be cool to hear from matplotlib what their experience was. I'm not sure I'm for dropping 2.6 for the sake of dropping 2.6. What would we actually gain? There are two fixes in sklearn/utils/fixes.py that we could remove, I think. Also: what does dropping 2.6 mean?