You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As January 1st approaches, support for "Python 2" gets to its end. By deprecating it we can free some machine/time on CI and maybe simplify our "dependency matrix"
Note that this issue is not meant to be executed before the January 1st 2020. The early public issue is just to track it and talk/communicate about.
dropping support for Python 2 also allows to employ language features for better readability, like dict comprehensions, set literals; new-style classes should be used and might provide leverage for further improvements.
why would the support for Python 2.7 be dropped when Python 3.2 and 3.4 is still supported though they reached their eol.
@funkyfuture I agree with the first remark, and for the second, I don't see any problem on dropping that.
The point here is just that dropping 3.2 and 3.4 will just impact the setup.py and not the compose code itself, like removing all the six conditions inside the code that would be a fairly big PR
dropping support for Python 2 also allows to employ language features for better readability, like dict comprehensions, set literals; new-style classes should be used and might provide leverage for further improvements.
I'm not arguing against dropping Python 2 support, but all of these language features are already supported on Python 2.
Activity
funkyfuture commentedon Sep 11, 2019
two quick remarks:
dropping support for Python 2 also allows to employ language features for better readability, like dict comprehensions, set literals; new-style classes should be used and might provide leverage for further improvements.
why would the support for Python 2.7 be dropped when Python 3.2 and 3.4 is still supported though they reached their eol.
ulyssessouza commentedon Sep 11, 2019
@funkyfuture I agree with the first remark, and for the second, I don't see any problem on dropping that.
The point here is just that dropping 3.2 and 3.4 will just impact the
setup.pyand not the compose code itself, like removing all thesixconditions inside the code that would be a fairly big PRRemoved Python2 support
Prepare drop of python 2.x support
Prepare drop of python 2.x support
Removed Python2 support
[-]Deprecate Python2[/-][+]Remove Python2[/+]agronholm commentedon Nov 30, 2019
I'm not arguing against dropping Python 2 support, but all of these language features are already supported on Python 2.
ndeloof commentedon Nov 30, 2019
There's probably many places a pure python 3 codebase could offer improvements, but my main motivation here is to reduce the maintenance effort.
SuperSandro2000 commentedon Nov 30, 2019
and Python 2.7 is EOL and is going to be removed from the next Debian and Ubuntu releases.
Prepare drop of python 2.x support
5 remaining items
Rebasing docker#7031 into current development on 1.26.x
Rebasing docker#7031 into 1.26.x
Rebasing docker#7031 into 1.26.x
Rebasing docker#7031 into 1.26.x
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support
Removed Python2 support