Remove Python2 · Issue #6890 · docker/compose · GitHub
Skip to content

Remove Python2 #6890

Closed

Description

@ulyssessouza

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.

Describe the solution you'd like

  • Remove py2 from the build matrix in Jenkins
  • Remove Python 2 from setup.py
  • Remove six from requirements.txt
  • Remove the announcement banner in README.md

Activity

  1. funkyfuture commented on Sep 11, 2019

    @funkyfuture

    two quick remarks:

    1. 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.

    2. 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.

  2. ulyssessouza commented on Sep 11, 2019

    @ulyssessouza
    ContributorAuthor

    @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

  3. added this to the 1.25.0 milestone on Oct 30, 2019
  4. modified the milestones: 1.25.0, 1.26.0 on Nov 14, 2019
  5. added a commit that references this issue on Nov 19, 2019
    d94c0da
  6. changed the title [-]Deprecate Python2[/-] [+]Remove Python2[/+] on Nov 21, 2019
  7. agronholm commented on Nov 30, 2019

    @agronholm

    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.

  8. ndeloof commented on Nov 30, 2019

    @ndeloof
    Contributor

    There's probably many places a pure python 3 codebase could offer improvements, but my main motivation here is to reduce the maintenance effort.

  9. SuperSandro2000 commented on Nov 30, 2019

    @SuperSandro2000

    and Python 2.7 is EOL and is going to be removed from the next Debian and Ubuntu releases.

  10. added a commit that references this issue on Dec 6, 2019
  11. 5 remaining items

  12. added 2 commits that reference this issue on Mar 11, 2020
    cfeb464
    e3e4c86
  13. added 2 commits that reference this issue on Mar 14, 2020
    cae4b70
    066988d
  14. added a commit that references this issue on Jun 3, 2020
    e8424d5
  15. added 4 commits that reference this issue on Jun 18, 2020
    05673ae
    c1dfb0b
    3ddcc25
    ec66c1b
  16. added 3 commits that reference this issue on Aug 5, 2020
    8f7d7d1
    db01591
    4d3d9f6
  17. added a commit that references this issue on Aug 21, 2020
    4419cc8
  18. added a commit that references this issue on Aug 21, 2020
    1285960
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions