Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.2.1 to 3.2.2. <details> <summary>Changelog</summary> Sourced from <a href="https://github.com/pyparsing/pyparsing/blob/master/CHANGES">pyparsing's changelog</a>. <blockquote> <h2>Version 3.2.2 - March, 2025</h2> <ul> <li> Released <code>cvt_pyparsing_pep8_names.py</code> conversion utility to upgrade pyparsing-based programs and libraries that use legacy camelCase names to use the new PEP8-compliant snake_case method names. The converter can also be imported into other scripts as <pre><code> from pyparsing.tools.cvt_pyparsing_pep8_names import pep8_converter </code></pre> </li> <li> Fixed bug in <code>nested_expr</code> where nested contents were stripped of whitespace when the default whitespace characters were cleared (raised in this StackOverflow question <a href="https://stackoverflow.com/questions/79327649">https://stackoverflow.com/questions/79327649</a> by Ben Alan). Also addressed bug in resolving PEP8 compliant argument name and legacy argument name. </li> <li> Fixed bug in <code>rest_of_line</code> and the underlying <code>Regex</code> class, in which matching a pattern that could match an empty string (such as <code>".*"</code> or <code>"[A-Z]*"</code> would not raise a <code>ParseException</code> at or beyond the end of the input string. This could cause an infinite parsing loop when parsing <code>rest_of_line</code> at the end of the input string. Reported by user Kylotan, thanks! (Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/593">#593</a>) </li> <li> Enhancements and extra input validation for <code>pyparsing.util.make_compressed_re</code> - see usage in <code>examples/complex_chemical_formulas.py</code> and result in the generated railroad diagram <code>examples/complex_chemical_formulas_diagram.html</code>. Properly escapes characters like "." and "*" that have special meaning in regular expressions. </li> <li> Fixed bug in <code>one_of()</code> to properly escape characters that are regular expression markers (such as '*', '+', '?', etc.) before building the internal regex. </li> <li> Better exception message for <code>MatchFirst</code> and <code>Or</code> expressions, showing all alternatives rather than just the first one. Fixes Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/592">#592</a>, reported by Focke, thanks! </li> <li> Added return type annotation of "-> None" for all <code>__init__()</code> methods, to satisfy <code>mypy --strict</code> type checking. PR submitted by FeRD, thank you! </li> <li> Added optional argument <code>show_hidden</code> to <code>create_diagram</code> to show elements that are used internally by pyparsing, but are not part of the actual parser grammar. For instance, the <code>Tag</code> class can insert values into the parsed results but it does not actually parse any input, so by default it is not included in a railroad diagram. By calling <code>create_diagram</code> with <code>show_hidden</code> = <code>True</code>, these internal elements will be included. (You can see this in the tag_metadata.py script in the examples directory.) </li> <li> Fixed bug in <code>number_words.py</code> example. Also added <code>ebnf_number_words.py</code> to demonstrate using the <code>ebnf.py</code> EBNF parser generator to build a similar parser directly from EBNF. </li> <li> Fixed syntax warning raised in <code>bigquery_view_parser.py</code>, invalid escape sequence "\s". Reported by sameer-google, nice catch! (Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/598">#598</a>) </li> <li> Added support for Python 3.14. </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pyparsing/pyparsing/commit/b0a8be6b031b9948eab10438dec4face566b52da"><code>b0a8be6</code></a> Prep for 3.2.2 release</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/f3abd5e86cd6352eeae7e329323a9e0392dd30a9"><code>f3abd5e</code></a> Changes to adventureEngine.py to make a better diagram</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/0a030b411a3703a5492476651799f41337be8c3f"><code>0a030b4</code></a> Some code cleanup, black</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/52ed22473b43f4ba6f88b2bf101bb1f5ef1b6a2b"><code>52ed224</code></a> Update docs with PEP8 names</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/274ed9840bfc841c7af0b937abbe24d4fb279b06"><code>274ed98</code></a> Fix one_of to use re.escape when merging strings into a regular expression</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/0f4c884e7c64410a6c29d6151454827c6207a5ed"><code>0f4c884</code></a> Add <code>non_capturing_groups</code> argument and extra input validation to `pyparsing....</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/67d3078c6fce59f2bc03b762220ea4eea8463c40"><code>67d3078</code></a> Some code cleanup in Forward._generateDefaultName and srange</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/28ef77eb0392ec592a0a22a770a95ef9405c9ef1"><code>28ef77e</code></a> Rewrite to remove return from finally block (Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/578">#578</a>)</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/626cca75e362109a6d9f64e725c57bd0c678fcab"><code>626cca7</code></a> Convert mayReturnEmpty to computed property, for proper handling of Regex exp...</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/4bb24bafd35bf41a3fe206d253cfda46d57df8ab"><code>4bb24ba</code></a> Removed cached_property definition of mayReturnEmpty (conflicted with attribu...</li> <li>Additional commits viewable in <a href="https://github.com/pyparsing/pyparsing/compare/3.2.1...3.2.2">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyparsing&package-manager=pip&previous-version=3.2.1&new-version=3.2.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> 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 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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>