Bump pyparsing from 2.2.0 to 3.2.3

[dependabot]

Bumps pyparsing from 2.2.0 to 3.2.3.

Release notes

Sourced from pyparsing's releases.

Pyparsing 3.1.0a1

NOTE: In the future release 3.2.0, use of many of the pre-PEP8 methods (such as ParserElement.parseString) will start to raise DeprecationWarnings. 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.)

Version 3.2.0 will also discontinue support for Python versions 3.6 and 3.7.

• API ENHANCEMENT: Optional(expr) may now be written as expr | ""

  This will make this code:

  "{" + Optional(Literal("A") | Literal("a")) + "}"
  

  writable as:

  "{" + (Literal("A") | Literal("a") | "") + "}"
  

  Some related changes implemented as part of this work:

  • Literal("") now internally generates an Empty() (and no longer raises an exception)
  • Empty is now a subclass of Literal

  Suggested by Antony Lee (issue #412), PR (#413) by Devin J. Pohly.

• Added new class property identifier to all Unicode set classes in pyparsing.unicode, using the class's values for cls.identchars and cls.identbodychars. Now Unicode-aware parsers that formerly wrote:

  ppu = pyparsing.unicode
  ident = Word(ppu.Greek.identchars, ppu.Greek.identbodychars)
  

  can now write:

  ident = ppu.Greek.identifier
  # or
  # ident = ppu.Ελληνικά.identifier
  

• Reworked delimited_list function into the new DelimitedList class. DelimitedList has the same constructor interface as delimited_list, and in this release, delimited_list changes from a function to a synonym for DelimitedList. delimited_list and the older delimitedList method will be deprecated in a future release, in favor of DelimitedList.

• Added new class method ParserElement.using_each, to simplify code that creates a sequence of Literals, Keywords, or other ParserElement subclasses.

  For instance, to define suppressable punctuation, you would previously write:

  LPAR, RPAR, LBRACE, RBRACE, SEMI = map(Suppress, "(){};")
  

  You can now write:

  LPAR, RPAR, LBRACE, RBRACE, SEMI = Suppress.using_each("(){};")
  

  using_each 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:

  algebra_var = MatchFirst(
      Char.using_each(string.ascii_lowercase, as_keyword=True)
  )
  

... (truncated)

Changelog

Sourced from pyparsing's changelog.

Version 3.2.3 - March, 2025

• Fixed bug released in 3.2.2 in which nested_expr could overwrite parse actions for defined content, and could truncate list of items within a nested list. Fixes Issue #600, reported by hoxbro and luisglft, with helpful diag logs and repro code.

Version 3.2.2 - March, 2025

• Released cvt_pyparsing_pep8_names.py 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

    from pyparsing.tools.cvt_pyparsing_pep8_names import pep8_converter
  

• Fixed bug in nested_expr where nested contents were stripped of whitespace when the default whitespace characters were cleared (raised in this StackOverflow question https://stackoverflow.com/questions/79327649 by Ben Alan). Also addressed bug in resolving PEP8 compliant argument name and legacy argument name.

• Fixed bug in rest_of_line and the underlying Regex class, in which matching a pattern that could match an empty string (such as ".*" or "[A-Z]*" would not raise a ParseException at or beyond the end of the input string. This could cause an infinite parsing loop when parsing rest_of_line at the end of the input string. Reported by user Kylotan, thanks! (Issue #593)

• Enhancements and extra input validation for pyparsing.util.make_compressed_re - see usage in examples/complex_chemical_formulas.py and result in the generated railroad diagram examples/complex_chemical_formulas_diagram.html. Properly escapes characters like "." and "*" that have special meaning in regular expressions.

• Fixed bug in one_of() to properly escape characters that are regular expression markers (such as '*', '+', '?', etc.) before building the internal regex.

• Better exception message for MatchFirst and Or expressions, showing all alternatives rather than just the first one. Fixes Issue #592, reported by Focke, thanks!

• Added return type annotation of "-> None" for all __init__() methods, to satisfy mypy --strict type checking. PR submitted by FeRD, thank you!

• Added optional argument show_hidden to create_diagram to show elements that are used internally by pyparsing, but are not part of the actual parser grammar. For instance, the Tag 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 create_diagram with show_hidden = True, these internal elements will be included. (You can see this in the tag_metadata.py script in the examples directory.)

• Fixed bug in number_words.py example. Also added ebnf_number_words.py to demonstrate

... (truncated)

Commits

• 4dace94 Fixed bug in nested_expr introduced in 3.2.2, fixes #600
• 3b3ca8d Prep for 3.2.3 development
• b0a8be6 Prep for 3.2.2 release
• f3abd5e Changes to adventureEngine.py to make a better diagram
• 0a030b4 Some code cleanup, black
• 52ed224 Update docs with PEP8 names
• 274ed98 Fix one_of to use re.escape when merging strings into a regular expression
• 0f4c884 Add non_capturing_groups argument and extra input validation to `pyparsing....
• 67d3078 Some code cleanup in Forward._generateDefaultName and srange
• 28ef77e Rewrite to remove return from finally block (Issue #578)
• Additional commits viewable in compare view

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 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 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)