Bump pyparsing from 3.0.9 to 3.1.0

[dependabot]

Bumps pyparsing from 3.0.9 to 3.1.0.

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.1.0 - June, 2023

• Added tag_emitter.py to examples. This example demonstrates how to insert tags into your parsed results that are not part of the original parsed text.

Version 3.1.0b2 - May, 2023

• Updated create_diagram() code to be compatible with railroad-diagrams package version 3.0. Fixes Issue #477 (railroad diagrams generated with black bars), reported by Sam Morley-Short.

• Fixed bug in NotAny, where parse actions on the negated expr were not being run. This could cause NotAny 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 #482, raised by byaka, thank you!

• Fixed create_diagram() to accept keyword args, to be passed through to the template.render() method to generate the output HTML (PR submitted by Aussie Schnore, good catch!)

• Fixed bug in python_quoted_string regex.

• Added examples/bf.py Brainf*ck parser/executor example. Illustrates using a pyparsing grammar to parse language syntax, and attach executable AST nodes to the parsed results.

Version 3.1.0b1 - April, 2023

• Added support for Python 3.12.

• API CHANGE: A slight change has been implemented when unquoting a quoted string parsed using the QuotedString 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 #474 raised by jakeanq, thanks!

• Added named field "url" to pyparsing.common.url, returning the entire parsed URL string.

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

  expr = Literal("X").add_parse_action(lambda tokens: "")("value")
  result = expr.parse_string("X")
  print(result["value"])
  

... (truncated)

Commits

• d5aafc3 Address warnings in test_simple_unit.py and lucene_grammar.py raised when run...
• e4f3ce2 Prep for 3.1.0 release
• 40babe0 More example updates, PEP-8 names, f-strings.
• 85c2ef1 Minor formatting change, bug-fix on 0000 time
• 2fc41a0 Update ci.yml
• 08e7cfd Minor changes in examples, conversion to PEP8 names, etc.
• a8b05cc Slight perf enhancement in Empty
• 801863a Make htmlStripper.py and html_table_parser examples use PEP-8 names, add comm...
• 7d4da80 Prep for release
• be0310a Add bf parser/executor example
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[codecov]

Codecov Report

Merging #128 (eb3315a) into dev_bjorn (3a8a617) will decrease coverage by 0.19%.
The diff coverage is 81.08%.

Additional details and impacted files

@@              Coverage Diff              @@
##           dev_bjorn     #128      +/-   ##
=============================================
- Coverage      93.17%   92.98%   -0.19%     
=============================================
  Files             36       36              
  Lines           3603     3608       +5     
  Branches         558      558              
=============================================
- Hits            3357     3355       -2     
- Misses           210      217       +7     
  Partials          36       36              

Impacted Files	Coverage Δ
src/pydna/sequence_picker.py	0.00% <ø> (ø)
src/pydna/dseq.py	95.18% <78.12%> (-1.57%)	⬇️
src/pydna/amplify.py	98.65% <100.00%> (-0.01%)	⬇️
src/pydna/assembly.py	97.59% <100.00%> (ø)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.