Re: [DISCUSS] PIP-155: Drop support for Python2
+1 Enrico Il Sab 16 Apr 2022, 21:47 Chris Bartholomew ha scritto: > +1 > On Saturday, April 16, 2022, 02:23:48 PM EDT, Dave Fisher < > w...@apache.org> wrote: > > +1 > > Sent from my iPhone > > > On Apr 16, 2022, at 11:15 AM, Matteo Merli > 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 > > > > > >> On Fri, Apr 15, 2022 at 5:34 PM PengHui Li wrote: > >> > >> +1 > >> > >> Penghui > >> > >>> On Sat, Apr 16, 2022 at 12:06 AM 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 > >>> > >>> > >
Re: [DISCUSS] PIP-155: Drop support for Python2
+1 Thanks, Yunze > 2022年4月16日 00:06，Matteo Merli 写道： > > 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 >
Re: [DISCUSS] PIP-155: Drop support for Python2
+1 Thanks, Hang Yunze Xu 于2022年4月18日周一 02:45写道： > > +1 > > Thanks, > Yunze > > > > > > 2022年4月16日 00:06，Matteo Merli 写道： > > > > 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 > > >
Re: [ANNOUNCE] New Committer: Zike Yang
Thank you all! Very glad to be the pulsar committer. Thanks, Zike Yang On Fri, Apr 15, 2022 at 10:53 AM Huanli Meng wrote: > > Good for you, Zike. Congratulations. > > BR//Huanli > > > On Apr 14, 2022, at 9:28 AM, Yu wrote: > > > > Congrats Zike! Well deserved! > > > > On Wed, Apr 13, 2022 at 7:00 PM Enrico Olivelli wrote: > > > >> Congratulations > >> > >> Enrico > >> > >> Il Mer 13 Apr 2022, 12:38 Hang Chen ha scritto: > >> > >>> Congrats Zike! > >>> > >>> Best, > >>> Hang > >>> > >>> Haiting Jiang 于2022年4月13日周三 18:16写道： > > Congrats! > > Thanks, > Haiting > > On 2022/04/13 09:34:23 PengHui Li wrote: > > The Apache Pulsar Project Management Committee (PMC) has invited Zike > >>> Yang > > https://github.com/RobertIndie to become a committer and we are > >>> pleased to > > announce that he has accepted. > > > > Welcome and Congratulations, Zike Yang! > > > > Please join us in congratulating and welcoming Zike Yang onboard! > > > > Best Regards, > > Penghui Li on behalf of the Pulsar PMC > > > >>> > >> >
Re: [ANNOUNCE] New Committer: Zike Yang
Hi, zike, congratulations! Ran Gao Best On 2022/04/13 09:34:23 PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Zike Yang > https://github.com/RobertIndie to become a committer and we are pleased to > announce that he has accepted. > > Welcome and Congratulations, Zike Yang! > > Please join us in congratulating and welcoming Zike Yang onboard! > > Best Regards, > Penghui Li on behalf of the Pulsar PMC >
Re: [ANNOUNCE] New Committer: Ruguo Yu
Congratulations! Ran Best On 2022/04/15 10:06:44 Yu wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Ruguo Yu ( > https://github.com/yuruguo) to become a committer and we are pleased to > announce that he has accepted. > > Welcome and Congratulations, Ruguo Yu! > > Please join us in congratulating and welcoming Ruguo Yu onboard! > > Best Regards, > > Yu on behalf of the Pulsar PMC >
Re: [DISCUSS] PIP-155: Drop support for Python2
+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 > >
Re: [VOTE] PIP-149: Making the REST Admin API fully async
+1
Ran Gao
On 2022/03/25 02:13:26 mattison chao wrote:
> This is the voting thread for PIP-149. It will stay open for at least 48
> hours.
>
> https://github.com/apache/pulsar/issues/14365
>
> Pasted below for quoting convenience.
>
> -
>
> Motivation
>
> The Rest API was originally designed to be implemented asynchronously, but
> with the iteration of functions, some synchronous implementations were
> added, resulting in many asynchronous methods called synchronous
> implementations. Also, many synchronous calls do not add timeouts. This
> greatly reduces concurrency, user operations, and experience.
> In order to prevent more problems, and improve code readability and
> maintainability, we intend to refactor these synchronous calls and
> standardize the implementation of the API.
>
> Related discussion:
> https://lists.apache.org/thread/pkkz2jgwtzpksp6d4rdm1pyxzb3z6vmg
>
> Goals
>
> Try to avoid synchronous method calls in asynchronous methods.
> Async variable (AsyncResponse) is placed in the first parameter position.
> Async variable (AsyncResponse) cannot be substituted into method
> implementations.
> Add more tests and increase the coverage.
> Modification
> Avoid synchronous method calls in asynchronous methods.
>
> protected void internalDeleteNamespace(boolean authoritative) {
>validateTenantOperation(namespaceName.getTenant(),
> TenantOperation.DELETE_NAMESPACE);
>validatePoliciesReadOnlyAccess();
> }
> Suggest to do like this:
>
> protected CompletableFuture internalDeleteNamespace(boolean
> authoritative) {
> return validateTenantOperationAsync(namespaceName.getTenant(),
> TenantOperation.DELETE_NAMESPACE)
>.thenCompose(__ -> validatePoliciesReadOnlyAccessAsync());
> }
> Async variable (AsyncResponse) is placed in the first parameter position
>
> public void deleteNamespace(@Suspended final AsyncResponse asyncResponse,
> @PathParam("tenant") String tenant,
> @PathParam("namespace") String namespace,
> @QueryParam("force") @DefaultValue("false") boolean force,
> @QueryParam("authoritative") @DefaultValue("false") boolean
> authoritative) {
>
> Async variable (AsyncResponse) cannot be substituted into method
> implementations
>
> internalCreateNonPartitionedTopicAsync(asyncResponse, authoritative,
> properties);
> Suggest to do like this:
>
> internalCreateNonPartitionedTopicAsync(authoritative, properties)
> .thenAccept(__ ->
> asyncResponse.resume(Response.noContent().build()))
> .exceptionally(ex -> {
> resumeAsyncResponseExceptionally(asyncResponse, ex.getCause());
> return null;
> });
>
> Task tracking
> In order to unify the modification and track the modified part, it's better
> to open an issue to track, like #14353, #14013, #13854.
>
> ---
> Best,
> Mattison
>
Re: [ANNOUNCE] New Committer: Zhangmin Gao
+1 Best, Ran Gao On 2022/04/13 09:35:57 PengHui Li wrote: > The Apache Pulsar Project Management Committee (PMC) has invited Zhangmin > Gao > https://github.com/gaozhangmin to become a committer and we are pleased to > announce that he has accepted. > > Welcome and Congratulations, Zhangmin Gao! > > Please join us in congratulating and welcoming Zhangmin Gao onboard! > > Best Regards, > Penghui Li on behalf of the Pulsar PMC >
Re: [DISCUSS] [PIP-154] Max active transaction limitation for transaction coordinator
Bo, Great work! +1 best, Ran Gao On 2022/04/12 12:44:36 丛搏 wrote: > pipHi Pulsar community, > > I open a pip to discuss Max active transaction limitation for > transaction coordinator. > link: https://github.com/apache/pulsar/issues/15133 > > > Thanks, > Bo >
[ANNOUNCE] Apache Pulsar 2.9.2 released
The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.2. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, it also provides transaction feature since 2.8.0, guaranteed exactly-once semantics for producing and consuming process over topics, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://pulsar.apache.org/download Release Notes are at: https://pulsar.apache.org/release-notes We would like to thank the contributors that made the release possible. Regards, The Pulsar Team
