-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
COMPAT: drop support for python 2.6 #7718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
let's wait / defer the decision on this till next version. I don't think this is a problem (until numpy < 1.7) |
Cool sounds good |
any objections to slating this for 0.18.0 (prob next year) cc @jorisvandenbossche @cpcloud @shoyer @wesm @sinhrks @TomAugspurger |
Sounds fine to me. |
and conda no longer building for 2.6 (though I can build those as well) |
Fine by me On Fri, Oct 9, 2015 at 1:15 PM Wes McKinney [email protected]
|
As a data point, mpl is dropping support for py2.6 with 1.5/2.0. Both should still work with 2.6, but our 2.1 is going to include things which break on 2.6 (traitlets and ordered dicts). Sorry to be forcing your hand here a bit. |
@tacaswell no, its really that lots of others are dropping this support, e.g. conda builds and such. We don't have to do this, but its been slated for a while. |
COMPAT: drop suppport for python 2.6, #7718
This is just matching Pandas 0.18. pandas-dev/pandas#7718 pandas-dev/pandas#11273
will close #8760 at same time
The slowest of the slow of Linux distributions (RHEL) has upgraded their version of Python to 2.7. I think if they're happy with not supporting 2.6, then we can be too. Supporting it is not a huge deal, but it would be nice to really encourage people to move forward with upgrading to later versions of Python which would provide the community with momentum towards Python 3. While we can't force everyone to use Python 3, I think dropping support for Python 2.6 is reasonable. The last binary release of Python 2.6 was 2.6.6 and that was in 2010. By now, most people are using python 2.7.
The text was updated successfully, but these errors were encountered: