Visitar URL original
PIP-155: Drop support for Python2 · Issue #15185 · apache/pulsar · GitHub
Skip to content

PIP-155: Drop support for Python2 #15185

Closed

Description

@merlimat

Motivation

Python 2.x has been deprecated for many years now and it was officially end-of-lifed 2.5 years ago (https://www.python.org/doc/sunset-python-2/).

We have well reached the point by which we need to drop Python 2.7 compatibility for Pulsar client and for Pulsar functions.

Based on Python end-of-life policies, there are 4 versions of Python that are currently supported: 3.7, 3.8, 3.9 and 3.10. https://endoflife.date/python

That gives a 5 years support schedule from release to EoL.

Goal

Support only the last 4 Python releases Pulsar client and for Pulsar functions, currently 3.7, 3.8, 3.9 and 3.10. Once 3.7 reaches end-of-life, it will be dropped by Pulsar too.

This policy will be also applied to the Pulsar patch releases which will stop providing Python wheel files for the deprecated versions.

API Changes

No changes at this time, though Pulsar Python client library will be now free to use Python3 specific syntaxes and libraries.

Changes

  1. Switch the CI build to run Python client lib tests with Python3
  2. Switch integration tests to use Python3
  3. Stop building and distributing wheel files for Python 2.7

Activity

  1. added this to the 2.11.0 milestone on Apr 15, 2022
  2. zbentley commented on Apr 15, 2022

    @zbentley
    Contributor

    Thoughts on minimum py3 version? 3.6+ and 3.7+ are common choices in the python ecosystem.

  3. merlimat commented on Apr 15, 2022

    @merlimat
    ContributorAuthor

    Do you know where to find a list of feature/syntax that were changed in 3.6 or 3.7?
    As in: what could we be free to use if we didn't have to support Py 3.5 and 3.6?

  4. zbentley commented on Apr 15, 2022

    @zbentley
    Contributor
  5. merlimat commented on Apr 16, 2022

    @merlimat
    ContributorAuthor

    This is actually helpful: https://endoflife.date/python

    3.6 has already reached end of life and here will be no more security updates. It does indeed make sense for us to stop supporting it too.

  6. github-actions commented on May 21, 2022

    @github-actions

    The issue had no activity for 30 days, mark with Stale label.

  7. github-actions commented on Jun 20, 2022

    @github-actions

    The issue had no activity for 30 days, mark with Stale label.

  8. modified the milestones: 2.11.0, 2.12.0 on Jul 26, 2022
  9. dimaqq commented on Sep 9, 2022

    @dimaqq

    Poke

  10. tisonkun commented on Dec 7, 2022

    @tisonkun
    Member

    Closed as resolved. I don't find outstanding dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions