+1 Sent from my iPhone
> On Apr 16, 2022, at 11:15 AM, Matteo Merli <matteo.me...@gmail.com> wrote: > > Adding a bit on which Python versions to support, I found this very > helpful: https://endoflife.date/python > > Basically 3.5 and 3.6 releases have already reached end-of-life as > well and there will be no more security updates. It does indeed make > sense for us to stop supporting them too. > > I would update this proposal to use 3.7 as the oldest supported Python > release and to keep supporting only the last 4 Python releases, > following the Python EOL schedule (5 years from release to EOL). > > So right now: 3.7, 3.8, 3.9 and 3.10. > Once 3.11 is out and 3.7 reaches EOL, we drop 3.7. > > > -- > Matteo Merli > <matteo.me...@gmail.com> > >> On Fri, Apr 15, 2022 at 5:34 PM PengHui Li <peng...@apache.org> wrote: >> >> +1 >> >> Penghui >> >>> On Sat, Apr 16, 2022 at 12:06 AM Matteo Merli <mme...@apache.org> 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> >>>
