Skip to content

Drop support for Python 2 #1054

Description

@palnabarun

Python 2 has reached End of Life as of January 1, 2020 and we are still supporting it. Releasing future versions of the client and maintaining released versions with Python 2 support might lead to problems for downstream users.

My suggestion is to stop releasing the client with Python 2 support and removing Python 2.7 from CI/CD.

Also, it would be helpful if we provide a warning message in the README against using Python 2 versions of already released client versions.

Activity

  1. palnabarun commented on Jan 10, 2020

    @palnabarun
    MemberAuthor

    /assign

  2. palnabarun commented on Jan 10, 2020

    @palnabarun
    MemberAuthor
  3. micw523 commented on Jan 10, 2020

    @micw523
    Contributor

    I think we should probably wait till v12 stable is released to accommodate a client version for server version v1.16, which brought many breaking changes. What do you think?
    /assign

  4. yliaog commented on Jan 10, 2020

    @yliaog
    Contributor

    it's good to stop supporting python 2 in next release. before that, please make an announcement about it in dev mailing list and slack channel.

  5. palnabarun commented on Jan 10, 2020

    @palnabarun
    MemberAuthor

    I think we should probably wait till v12 stable is released to accommodate a client version for server version v1.16, which brought many breaking changes. What do you think?

    I agree. We can do that.

  6. palnabarun commented on Jan 10, 2020

    @palnabarun
    MemberAuthor

    it's good to stop supporting python 2 in next release. before that, please make an announcement about it in dev mailing list and slack channel.

    Sure. I will draft an email and get it reviewed in the next meeting.

  7. fabianvf commented on Jan 20, 2020

    @fabianvf
    Contributor

    My only concern with this is that we are seeing this bug consistently in Python 3, but not in Python 2, #1037

    With that issue resolved I would support dropping Python 2 support

  8. fejta-bot commented on Apr 19, 2020

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  9. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 19, 2020
  10. palnabarun commented on Apr 20, 2020

    @palnabarun
    MemberAuthor

    /remove-lifecycle stale

  11. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 20, 2020
  12. palnabarun commented on Apr 20, 2020

    @palnabarun
    MemberAuthor

    /lifecycle frozen

  13. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    on Apr 20, 2020
  14. palnabarun commented on Jun 22, 2020

    @palnabarun
    MemberAuthor

    The roadmap that we discussed in the previous meetings based on the comments here:

    1. Keep the support for Python 2 in Kubernetes Client v12.0.0
    2. Send a communication to the mailing list and slack channel about dropping support in future releases
    3. Drop support for Python 2 in Kubernetes Client v13.0.0

    Update
    This is planned for v18.0.0 now. A deprecation notice will be added to v17.0.0.

  15. booooh commented on Oct 15, 2020

    @booooh

    With 12.0.0 being released, is this planned for the next release?

  16. palnabarun commented on Nov 13, 2020

    @palnabarun
    MemberAuthor

    @booooh -- Yes. We are planning to add a deprecation notice in the next release and completely remove in the release after that.

  17. palnabarun commented on Oct 25, 2021

    @palnabarun
    MemberAuthor

    Python 2 support had been dropped since Client Version v18.17.0a1 with v18.20.0 being the first stable release. 🎉

    Ref: https://github.com/kubernetes-client/python/blob/master/CHANGELOG.md#v18200

    Hence, closing this.

  18. palnabarun commented on Oct 25, 2021

    @palnabarun
    MemberAuthor

    /remove-lifecycle frozen
    /close

  19. k8s-ci-robot commented on Oct 25, 2021

    @k8s-ci-robot
    Contributor

    @palnabarun: Closing this issue.

    Details

    In response to this:

    /remove-lifecycle frozen
    /close

    Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

  20. removed
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    on Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions