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 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 render our > code base much harder to understand and maintain over time. > > +1 for dropping 2.6 support in scikit-learn because of that. > > Also as a side note: PySpark developers plan to drop Python 2.6 > support in the future as well: > https://issues.apache.org/jira/browse/SPARK-12661 > ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Scikit-learn-general mailing list Scikit-learn-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
