You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2026/07/25 07:04:29 UTC
[PR] chore(deps): bump pyparsing from 3.2.3 to 3.3.2 [superset]
dependabot[bot] opened a new pull request, #42420:
URL: https://github.com/apache/superset/pull/42420
Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.2.3 to 3.3.2.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/pyparsing/pyparsing/blob/master/CHANGES">pyparsing's changelog</a>.</em></p>
<blockquote>
<h2>Version 3.3.2 - January, 2026</h2>
<ul>
<li>
<p>Defined pyparsing-specific warning classes so that they can be selectively enabled
or disabled without affecting warnings raised by other libraries in the same Python
app:</p>
<ul>
<li><code>PyparsingWarning</code> - base warning for all pyparsing-specific warnings (inherits
from <code>UserWarning</code>)</li>
<li><code>PyparsingDeprecationWarning</code> - warning for using deprecated features (inherits
from <code>PyparsingWarning</code> and <code>DeprecationWarning</code>)</li>
<li><code>PyparsingDiagnosticWarning</code> - warning raised when pyparsing diagnostics are
enabled and a diagnostic feature is used (inherits from <code>PyparsingWarning</code>)</li>
</ul>
</li>
<li>
<p>Added <code>as_datetime</code> parse action to <code>pyparsing.common</code> - a more generalized
version of the <code>convert_to_datetime</code> parse action (supports any expression that extracts
date/time fields into "year", "month", "day", etc. results names), and validates
that the parsed fields represent a valid date and time.</p>
</li>
<li>
<p>Added <code>iso8601_date_validated</code> and <code>iso8601_datetime_validated</code> expressions to
<code>pyparsing.common</code>, which return a Python <code>datetime.datetime</code></p>
</li>
<li>
<p>Various performance improvements in <code>ParseResults</code> class and core functions, with
10-20% performance overall.</p>
</li>
<li>
<p>Added <code>regex_inverter</code> web page (using PyScript) to demonstrate using the <code>inv_regex.py</code>
example.</p>
</li>
<li>
<p>Expanded regex forms handled by the <code>examples/inv_regex.py</code> example:</p>
<ul>
<li>named capturing groups (<code>?P<name></code>)</li>
<li>partial repetition (<code>{m,}</code> and <code>{,n}</code>)</li>
<li>negated character classes (<code>[^...]</code>)</li>
</ul>
</li>
<li>
<p>Added <code>SPy</code> (Simplified Python) parser to examples.</p>
</li>
</ul>
<h2>Version 3.3.1 - December, 2025</h2>
<ul>
<li>Added license info to metadata, following PEP-639. Thanks to Gedalia Pasternak and
Marc Mueller for submitted issue and PR. Fixes <a href="https://redirect.github.com/pyparsing/pyparsing/issues/626">#626</a>.</li>
</ul>
<h2>Version 3.3.0 - December, 2025</h2>
<p>===========================================================================================
The version 3.3.0 release will begin emitting <code>DeprecationWarnings</code> for pyparsing methods
that have been renamed to PEP8-compliant names (introduced in pyparsing 3.0.0, in August,
2021, with legacy names retained as aliases). In preparation, I added in pyparsing
3.2.2 a utility for finding and replacing the legacy method names with the new names.
This utility is located at <code>pyparsing/tools/cvt_pep8_names.py</code>. This script will scan all
Python files specified on the command line, and if the <code>-u</code> option is selected, will
replace all occurrences of the old method names with the new PEP8-compliant names,</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/pyparsing/pyparsing/commit/fa24016d953353f8ba566abb5c8fc12e1d07556c"><code>fa24016</code></a> Sync regex_inverter example from pyparsing</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/ea2204618ea09a49cf32ae0e51b338acf32c5d7c"><code>ea22046</code></a> Updates to regex_inverter example: handle cancel during long max_results inte...</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/7df5c0915620bfa2467e684fb05345a7349a7496"><code>7df5c09</code></a> Sync regex_inverter example from pyparsing</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/e862afaa0dc49415ecc7da395bf91dd27d13c73a"><code>e862afa</code></a> Add Regular Expressions Quick Reference to regex_inverter/index.html</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/6fdbd8828a5471c48ab645cb982f5a936345f8a4"><code>6fdbd88</code></a> Sync regex_inverter example from pyparsing</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/5b3304515a293238befe37e24e28c617ac855254"><code>5b33045</code></a> Add note in the regex inverter that only the 7-bit ASCII characters are used ...</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/e403f2c9d00de35f68b946da6eb55cb99ef41a37"><code>e403f2c</code></a> Merge branch 'master' of <a href="https://github.com/pyparsing/pyparsing">https://github.com/pyparsing/pyparsing</a></li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/e7b5f1c1660ec675c60ce1c1750798a25b6e8195"><code>e7b5f1c</code></a> Fix repo sync action in sync-regex-inverter.yml</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/ea463fa53936d64bc8618afdabd87120709f8c41"><code>ea463fa</code></a> Sync regex_inverter example from pyparsing</li>
<li><a href="https://github.com/pyparsing/pyparsing/commit/afcbdacfee7bc190bdd2354efa4c4dd1c6cfaf84"><code>afcbdac</code></a> Change repetition instructions to use {,4} instead of {,10}</li>
<li>Additional commits viewable in <a href="https://github.com/pyparsing/pyparsing/compare/3.2.3...3.3.2">compare view</a></li>
</ul>
</details>
<br />
[](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)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@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)
</details>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump pyparsing from 3.2.3 to 3.3.2 [superset]
Posted by "codecov[bot] (via GitHub)" <gi...@apache.org>.
codecov[bot] commented on PR #42420:
URL: https://github.com/apache/superset/pull/42420#issuecomment-5077588591
## [Codecov](https://app.codecov.io/gh/apache/superset/pull/42420?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 56.00%. Comparing base ([`8c37d62`](https://app.codecov.io/gh/apache/superset/commit/8c37d627aa9c8351e7e60611cd3e1219495bb830?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`c90b063`](https://app.codecov.io/gh/apache/superset/commit/c90b063d3eeac0fc1bf6b3835e23077f78c81acb?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
> :exclamation: There is a different number of reports uploaded between BASE (8c37d62) and HEAD (c90b063). Click for more details.
>
> <details><summary>HEAD has 101 uploads less than BASE</summary>
>
>| Flag | BASE (8c37d62) | HEAD (c90b063) |
>|------|------|------|
>|python|88|1|
>|presto|15|1|
></details>
<details><summary>Additional details and impacted files</summary>
```diff
@@ Coverage Diff @@
## master #42420 +/- ##
==========================================
- Coverage 65.24% 56.00% -9.25%
==========================================
Files 2795 2795
Lines 157643 157643
Branches 36061 36061
==========================================
- Hits 102853 88283 -14570
- Misses 52814 68535 +15721
+ Partials 1976 825 -1151
```
| [Flag](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
|---|---|---|
| [hive](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
| [mysql](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
| [postgres](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
| [presto](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `40.31% <ø> (ø)` | |
| [python](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `40.31% <ø> (-18.72%)` | :arrow_down: |
| [sqlite](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
| [unit](https://app.codecov.io/gh/apache/superset/pull/42420/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `?` | |
Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#carryforward-flags-in-the-pull-request-comment) to find out more.
</details>
[:umbrella: View full report in Codecov by Harness](https://app.codecov.io/gh/apache/superset/pull/42420?dropdown=coverage&src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
:loudspeaker: Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache).
<details><summary> :rocket: New features to boost your workflow: </summary>
- :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
- :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
</details>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump pyparsing from 3.2.3 to 3.3.2 [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42420:
URL: https://github.com/apache/superset/pull/42420#issuecomment-5077421738
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump pyparsing from 3.2.3 to 3.3.2 [superset]
Posted by "hainenber (via GitHub)" <gi...@apache.org>.
hainenber merged PR #42420:
URL: https://github.com/apache/superset/pull/42420
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [PR] chore(deps): bump pyparsing from 3.2.3 to 3.3.2 [superset]
Posted by "bito-code-review[bot] (via GitHub)" <gi...@apache.org>.
bito-code-review[bot] commented on PR #42420:
URL: https://github.com/apache/superset/pull/42420#issuecomment-5078094003
AI Code Review is in progress (usually takes 3 to 15 minutes unless it's a very large PR).
<details>
<summary>
Bito Usage Guide
</summary>
**Commands**
Type the following command in the pull request comment and save the comment.
- `/review` - Manually triggers a full AI review.
- `/pause` - Pauses automatic reviews on this pull request.
- `/resume` - Resumes automatic reviews.
- `/resolve` - Marks all Bito-posted review comments as resolved.
- `/abort` - Cancels all in-progress reviews.
Refer to the <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/available-commands" target="_blank" rel="noopener noreferrer">documentation</a> for additional commands.
**Configuration**
This repository uses `Superset` You can customize the agent settings <a href="https://alpha.bito.ai/home/ai-agents/code-review-agent" target="_blank" rel="noopener noreferrer">here</a> or contact your Bito workspace admin at evan@preset.io.
**Documentation & Help**
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/getting-started/install-run-using-bito-cloud/create-or-customize-an-agent-instance" target="_blank" rel="noopener noreferrer">Customize agent settings</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/implementing-custom-code-review-rules" target="_blank" rel="noopener noreferrer">Review rules</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent" target="_blank" rel="noopener noreferrer">General documentation</a>
- <a href="https://docs.bito.ai/bito-dev-agents/ai-code-review-agent/faqs" target="_blank" rel="noopener noreferrer">FAQ</a>
</details>
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org