Thank you for pushing this initiative through, Matteo. I agree that we should do this. I had started a draft PR about a month ago that would have helped, but I ran into some issues with the build [0]. I'm closing the PR now, but feel free to look at it in case it helps make your work easier.
Can we cherry pick these changes back to the older release branches (2.8, 2.9, and 2.10)? I don't see any reason to support python 2.7 for any future releases. Dropping support primarily saves release managers time when building the many different python clients. Thanks, Michael [0] https://github.com/apache/pulsar/pull/14827 On Mon, Apr 18, 2022 at 12:36 AM Ran Gao <r...@apache.org> wrote: > > +1 > > Ran Gao > > Best > > On 2022/04/15 16:06:36 Matteo Merli wrote: > > https://github.com/apache/pulsar/issues/15185 > > > > --------- > > > > ## 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. > > > > ## Goal > > > > Support only Python 3.5+ for Pulsar client and for Pulsar functions. > > > > ## 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 > > > > > > > > > > -- > > Matteo Merli > > <mme...@apache.org> > >
