Repository navigation
Drop support for Python 2.6 and Python 3.3 #580
Description
Activity
- pinned this issue
on Nov 27, 2020 We are a version compatibility layer, we should aim as much as is reasonable to cover the versions we can. This is not a compelling enough reason to drop py26/py33 in my opinion. It is better to change our CI system than it is to drop py26 and py33.
We are a version compatibility layer, we should aim as much as is reasonable to cover the versions we can.
That is true. As you can see, all history downloads of 2.6 and 3.3 are pretty tiny compared to other versions. I was trying to see if there is any downloads of python 2.6 and 3.3 after 2019 by
pypinfo --start-date 2019-01-01 future pyversion, but BigQuery is giving meQuota exceedederror.Anyway the downstream can still use
futurewith EOL'd python by pinning to an old version, e.g.future==0.18.2, so strictly speaking there is a work-around. As the Python community has moved on to Python 3 (dropping Python 2.7), I feel as an upstream library we should also move on by at least dropping Python 2.6 support on the main branch.No. We are not a typical upstream library. We should not drop support for python versions unless there's a compelling reason to do so. I see no such reason.
Similar to davidhalter/jedi#1016
Dropping support for EOL versions of Python.
Google BigQuery result for all history downloads by python version:
You can see that 2.6 and 3.3 are both ~0.0%, so it should be safe to drop. Worst case if anyone wants to use
futurefor Python 2.6 and Python 3.3, they can always use an older version offuture.Python 2.6 is blocking us from moving to Github Action, since Github's https://github.com/actions/setup-python does not support Python 2.6 anymore (see full list).