⬆️ Bump pyparsing from 3.0.6 to 3.0.7

[dependabot]

Bumps pyparsing from 3.0.6 to 3.0.7.

Release notes

Sourced from pyparsing's releases.

pyparsing 3.0.7

• Fixed bug #345, in which delimitedList changed expressions in place using expr.streamline(). Reported by Kim Gräsman, thanks!

• Fixed bug #346, when a string of word characters was passed to WordStart or WordEnd instead of just taking the default value. Originally posted as a question by Parag on StackOverflow, good catch!

• Fixed bug #350, in which White expressions could fail to match due to unintended whitespace-skipping. Reported by Fu Hanxi, thank you!

• Fixed bug #355, when a QuotedString is defined with characters in its quoteChar string containing regex-significant characters such as ., *, ?, [, ], etc.

• Fixed bug in ParserElement.run_tests where comments would be displayed using with_line_numbers.

• Added optional "min" and "max" arguments to delimited_list. PR submitted by Marius, thanks!

• Added new API change note in whats_new_in_pyparsing_3_0_0, regarding a bug fix in the bool() behavior of ParseResults.

  Prior to pyparsing 3.0.x, the ParseResults class implementation of __bool__ would return False if the ParseResults item list was empty, even if it contained named results. In 3.0.0 and later, ParseResults will return True if either the item list is not empty or if the named results dict is not empty.

  # generate an empty ParseResults by parsing a blank string with
  # a ZeroOrMore
  result = Word(alphas)[...].parse_string("")
  print(result.as_list())
  print(result.as_dict())
  print(bool(result))
  add a results name to the result
  result["name"] = "empty result"
  print(result.as_list())
  print(result.as_dict())
  print(bool(result))
  

  Prints:

  []
  {}
  False
  []
  {'name': 'empty result'}
  True
  

  In previous versions, the second call to bool() would return False.

• Minor enhancement to Word generation of internal regular expression, to emit consecutive characters in range, such as "ab", as "ab", not "a-b".

• Fixed character ranges for search terms using non-Western characters in booleansearchparser, PR submitted by tc-yu, nice work!

• Additional type annotations on public methods.

Changelog

Sourced from pyparsing's changelog.

Version 3.0.7 -

• Fixed bug #345, in which delimitedList changed expressions in place using expr.streamline(). Reported by Kim Gräsman, thanks!

• Fixed bug #346, when a string of word characters was passed to WordStart or WordEnd instead of just taking the default value. Originally posted as a question by Parag on StackOverflow, good catch!

• Fixed bug #350, in which White expressions could fail to match due to unintended whitespace-skipping. Reported by Fu Hanxi, thank you!

• Fixed bug #355, when a QuotedString is defined with characters in its quoteChar string containing regex-significant characters such as ., *, ?, [, ], etc.

• Fixed bug in ParserElement.run_tests where comments would be displayed using with_line_numbers.

• Added optional "min" and "max" arguments to delimited_list. PR submitted by Marius, thanks!

• Added new API change note in whats_new_in_pyparsing_3_0_0, regarding a bug fix in the bool() behavior of ParseResults.

  Prior to pyparsing 3.0.x, the ParseResults class implementation of __bool__ would return False if the ParseResults item list was empty, even if it contained named results. In 3.0.0 and later, ParseResults will return True if either the item list is not empty or if the named results dict is not empty.

  # generate an empty ParseResults by parsing a blank string with
  # a ZeroOrMore
  result = Word(alphas)[...].parse_string("")
  print(result.as_list())
  print(result.as_dict())
  print(bool(result))
  add a results name to the result
  result["name"] = "empty result"
  print(result.as_list())
  print(result.as_dict())
  print(bool(result))
  

  Prints:

  []
  {}
  False
  

... (truncated)

Commits

• 938f59d Fixed IndentedBlock internal parse action to use correct value of cur
• 236cb8b Fixed exception generated in a ParserElementEnhance if the contained expr is ...
• 5fb6e0d Fix #355 - needed re.escape, not escape_regex_range_chars in QuotedString
• 1ccf846 Issue #350 - fixed whitespace skipping around White expressions
• 30bd0f3 Some code cleanup, replacing map() calls with list comprehensions; better typ...
• 5771459 Fixed bug in ParserElement.run_tests where comments would be displayed using ...
• 5e3e1bb Fixed PEP-8 compatibility logic in WordStart and WordEnd (Issue #346)
• 3a12ded Update CHANGES doc with latest PR
• d72bd46 Fixing Unicode block range in examples/booleansearchparser.py (#342)
• 2f633f4 Fix #345 - delimitedList calling streamline() changes content of expr in some...
• 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 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)