dependabot[bot] opened a new pull request, #7963: URL: https://github.com/apache/iceberg/pull/7963
Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.0.9 to 3.1.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pyparsing/pyparsing/releases";>pyparsing's releases</a>.</em></p> <blockquote> <h2>Pyparsing 3.1.0a1</h2> <p>NOTE: In the future release 3.2.0, use of many of the pre-PEP8 methods (such as <code>ParserElement.parseString</code>) will start to raise <code>DeprecationWarnings</code>. 3.2.0 should get released some time later in 2023. I currently plan to completely drop the pre-PEP8 methods in pyparsing 4.0, though we won't see that release until at least late 2023 if not 2024. So there is plenty of time to convert existing parsers to the new function names before the old functions are completely removed. (Big help from Devin J. Pohly in structuring the code to enable this peaceful transition.)</p> <p>Version 3.2.0 will also discontinue support for Python versions 3.6 and 3.7.</p> <ul> <li> <p>API ENHANCEMENT: <code>Optional(expr)</code> may now be written as <code>expr | ""</code></p> <p>This will make this code:</p> <pre><code>"{" + Optional(Literal("A") | Literal("a")) + "}" </code></pre> <p>writable as:</p> <pre><code>"{" + (Literal("A") | Literal("a") | "") + "}" </code></pre> <p>Some related changes implemented as part of this work:</p> <ul> <li><code>Literal("")</code> now internally generates an <code>Empty()</code> (and no longer raises an exception)</li> <li><code>Empty</code> is now a subclass of <code>Literal</code></li> </ul> <p>Suggested by Antony Lee (issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/412";>#412</a>), PR (<a href="https://redirect.github.com/pyparsing/pyparsing/issues/413";>#413</a>) by Devin J. Pohly.</p> </li> <li> <p>Added new class property <code>identifier</code> to all Unicode set classes in <code>pyparsing.unicode</code>, using the class's values for <code>cls.identchars</code> and <code>cls.identbodychars</code>. Now Unicode-aware parsers that formerly wrote:</p> <pre><code>ppu = pyparsing.unicode ident = Word(ppu.Greek.identchars, ppu.Greek.identbodychars) </code></pre> <p>can now write:</p> <pre><code>ident = ppu.Greek.identifier # or # ident = ppu.Ελληνικά.identifier </code></pre> </li> <li> <p>Reworked <code>delimited_list</code> function into the new <code>DelimitedList</code> class. <code>DelimitedList</code> has the same constructor interface as <code>delimited_list</code>, and in this release, <code>delimited_list</code> changes from a function to a synonym for <code>DelimitedList</code>. <code>delimited_list</code> and the older <code>delimitedList</code> method will be deprecated in a future release, in favor of <code>DelimitedList</code>.</p> </li> <li> <p>Added new class method <code>ParserElement.using_each</code>, to simplify code that creates a sequence of <code>Literals</code>, <code>Keywords</code>, or other <code>ParserElement</code> subclasses.</p> <p>For instance, to define suppressable punctuation, you would previously write:</p> <pre><code>LPAR, RPAR, LBRACE, RBRACE, SEMI = map(Suppress, "(){};") </code></pre> <p>You can now write:</p> <pre><code>LPAR, RPAR, LBRACE, RBRACE, SEMI = Suppress.using_each("(){};") </code></pre> <p><code>using_each</code> will also accept optional keyword args, which it will pass through to the class initializer. Here is an expression for single-letter variable names that might be used in an algebraic expression:</p> <pre><code>algebra_var = MatchFirst( Char.using_each(string.ascii_lowercase, as_keyword=True) ) </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <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.1.0 - June, 2023</h2> <ul> <li>Added <code>tag_emitter.py</code> to examples. This example demonstrates how to insert tags into your parsed results that are not part of the original parsed text.</li> </ul> <h2>Version 3.1.0b2 - May, 2023</h2> <ul> <li> <p>Updated <code>create_diagram()</code> code to be compatible with railroad-diagrams package version 3.0. Fixes Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/477";>#477</a> (railroad diagrams generated with black bars), reported by Sam Morley-Short.</p> </li> <li> <p>Fixed bug in <code>NotAny</code>, where parse actions on the negated expr were not being run. This could cause <code>NotAny</code> to incorrectly fail if the expr would normally match, but would fail to match if a condition used as a parse action returned False. Fixes Issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/482";>#482</a>, raised by byaka, thank you!</p> </li> <li> <p>Fixed <code>create_diagram()</code> to accept keyword args, to be passed through to the <code>template.render()</code> method to generate the output HTML (PR submitted by Aussie Schnore, good catch!)</p> </li> <li> <p>Fixed bug in <code>python_quoted_string</code> regex.</p> </li> <li> <p>Added <code>examples/bf.py</code> Brainf*ck parser/executor example. Illustrates using a pyparsing grammar to parse language syntax, and attach executable AST nodes to the parsed results.</p> </li> </ul> <h2>Version 3.1.0b1 - April, 2023</h2> <ul> <li> <p>Added support for Python 3.12.</p> </li> <li> <p>API CHANGE: A slight change has been implemented when unquoting a quoted string parsed using the <code>QuotedString</code> class. Formerly, when unquoting and processing whitespace markers such as \t and \n, these substitutions would occur first, and then any additional '' escaping would be done on the resulting string. This would parse "\n" as "<newline>". Now escapes and whitespace markers are all processed in a single pass working left to right, so the quoted string "\n" would get unquoted to "\n" (a backslash followed by "n"). Fixes issue <a href="https://redirect.github.com/pyparsing/pyparsing/issues/474";>#474</a> raised by jakeanq, thanks!</p> </li> <li> <p>Added named field "url" to <code>pyparsing.common.url</code>, returning the entire parsed URL string.</p> </li> <li> <p>Fixed bug when parse actions returned an empty string for an expression that had a results name, that the results name was not saved. That is:</p> <pre><code>expr = Literal("X").add_parse_action(lambda tokens: "")("value") result = expr.parse_string("X") print(result["value"]) </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pyparsing/pyparsing/commit/d5aafc39a37f213971ba2b76ae7101ff3345b209";><code>d5aafc3</code></a> Address warnings in test_simple_unit.py and lucene_grammar.py raised when run...</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/e4f3ce2a0805bf1561b96b8f13210f07fe3651ab";><code>e4f3ce2</code></a> Prep for 3.1.0 release</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/40babe02aa8a7905c5b46d010888516036be02ab";><code>40babe0</code></a> More example updates, PEP-8 names, f-strings.</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/85c2ef19a3e11faad0cb405a5ab66bdca7e49f45";><code>85c2ef1</code></a> Minor formatting change, bug-fix on 0000 time</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/2fc41a02f32b4f7a769f036daec58ba4f233b106";><code>2fc41a0</code></a> Update ci.yml</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/08e7cfdb94fecf2d99c324856c37ec66fac0eeed";><code>08e7cfd</code></a> Minor changes in examples, conversion to PEP8 names, etc.</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/a8b05ccbe380117dac40b4cf6d9ffe08266fd7ed";><code>a8b05cc</code></a> Slight perf enhancement in Empty</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/801863aa4582a8ce5e6a7408d4966afcd247ea90";><code>801863a</code></a> Make htmlStripper.py and html_table_parser examples use PEP-8 names, add comm...</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/7d4da80b2bca8a2767134f4a181ea9aac4bbb230";><code>7d4da80</code></a> Prep for release</li> <li><a href="https://github.com/pyparsing/pyparsing/commit/be0310a83436bb4893d0068bb5da3059199e4c0b";><code>be0310a</code></a> Add bf parser/executor example</li> <li>Additional commits viewable in <a href="https://github.com/pyparsing/pyparsing/compare/pyparsing_3.0.9...3.1.0";>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 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) </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]
