[GitHub] [pulsar-test-infra] dependabot[bot] opened a new pull request, #30: Bump minimist from 1.2.5 to 1.2.6 in /doc-label-check
dependabot[bot] opened a new pull request, #30: URL: https://github.com/apache/pulsar-test-infra/pull/30 Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6. Commits https://github.com/substack/minimist/commit/7efb22a518b53b06f5b02a1038a88bd6290c2846";>7efb22a 1.2.6 https://github.com/substack/minimist/commit/ef88b9325f77b5ee643ccfc97e2ebda577e4c4e2";>ef88b93 security notice for additional prototype pollution issue https://github.com/substack/minimist/commit/c2b981977fa834b223b408cfb860f933c9811e4d";>c2b9819 isConstructorOrProto adapted from PR https://github.com/substack/minimist/commit/bc8ecee43875261f4f17eb20b1243d3ed15e70eb";>bc8ecee test from prototype pollution PR See full diff in https://github.com/substack/minimist/compare/1.2.5...1.2.6";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/pulsar-test-infra/network/alerts). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] PIP-155: Drop support for Python2
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 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 On Saturday, April 16, 2022, 02:23:48 PM EDT, Dave Fisher 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 >>> >>>
[GitHub] [pulsar-site] urfreespace merged pull request #51: feat: auto sync releases.json
urfreespace merged PR #51: URL: https://github.com/apache/pulsar-site/pull/51 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
