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 &quot;year&quot;, &quot;month&quot;, &quot;day&quot;, 
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&lt;name&gt;</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 />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyparsing&package-manager=pip&previous-version=3.2.3&new-version=3.3.2)](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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to