Bump pyparsing from 2.1.10 to 2.4.2

[dependabot-preview]

Bumps pyparsing from 2.1.10 to 2.4.2.

Release notes

Sourced from pyparsing's releases.

Pyparsing 2.4.2

Version 2.4.2 - July, 2019

• Updated the shorthand notation that has been added for repetition
  expressions: expr[min, max], with '...' valid as a min or max value:

  • expr[...] and expr[0, ...] are equivalent to ZeroOrMore(expr)
  • expr[1, ...] is equivalent to OneOrMore(expr)
  • expr[n, ...] or expr[n,] is equivalent
    to expr*n + ZeroOrMore(expr)
    (read as "n or more instances of expr")
  • expr[..., n] is equivalent to expr*(0, n)
  • expr[m, n] is equivalent to expr*(m, n)
    Note that expr[..., n] and expr[m, n] do not raise an exception
    if more than n exprs exist in the input stream. If this
    behavior is desired, then write expr[..., n] + ~expr.

  Better interpretation of [...] as ZeroOrMore raised by crowsonkb,
  thanks for keeping me in line!

  If upgrading from 2.4.1 or 2.4.1.1 and you have used expr[...]
  for OneOrMore(expr), it must be updated to expr[1, ...].

• The defaults on all the __diag__ switches have been set to False,
  to avoid getting alarming warnings. To use these diagnostics, set
  them to True after importing pyparsing.

  Example:

  import pyparsing as pp
  pp.__diag__.warn_multiple_tokens_in_named_alternation = True
  

• Fixed bug introduced by the use of getitem for repetition,
  overlooking Python's legacy implementation of iteration
  by sequentially calling getitem with increasing numbers until
  getting an IndexError. Found during investigation of problem
  reported by murlock, merci!

Pyparsing 2.4.2a1

Release candidate for 2.4.2:

• FIxes incorrect implementation of expr[…] as OneOrMore, changed to ZeroOrMore
• Fixes __getitem__-induced iterability for ParserElement class
• __diag__ flags are now all False by default

Pyparsing 2.4.1.1

This is a re-release of version 2.4.1 to restore the release history
in PyPI, since the 2.4.1 release was deleted.

There are 3 known issues in this release, which are fixed in
the upcoming 2.4.2:

... (truncated)

Changelog

Sourced from pyparsing's changelog.

Version 2.4.2 - July, 2019

• Updated the shorthand notation that has been added for repetition
  expressions: expr[min, max], with '...' valid as a min or max value:

  • expr[...] and expr[0, ...] are equivalent to ZeroOrMore(expr)
  • expr[1, ...] is equivalent to OneOrMore(expr)
  • expr[n, ...] or expr[n,] is equivalent
    to expr*n + ZeroOrMore(expr)
    (read as "n or more instances of expr")
  • expr[..., n] is equivalent to expr*(0, n)
  • expr[m, n] is equivalent to expr*(m, n)
    Note that expr[..., n] and expr[m, n] do not raise an exception
    if more than n exprs exist in the input stream. If this
    behavior is desired, then write expr[..., n] + ~expr.

  Better interpretation of [...] as ZeroOrMore raised by crowsonkb,
  thanks for keeping me in line!

  If upgrading from 2.4.1 or 2.4.1.1 and you have used expr[...]
  for OneOrMore(expr), it must be updated to expr[1, ...].

• The defaults on all the __diag__ switches have been set to False,
  to avoid getting alarming warnings. To use these diagnostics, set
  them to True after importing pyparsing.

  Example:

  import pyparsing as pp
  pp.__diag__.warn_multiple_tokens_in_named_alternation = True
  

• Fixed bug introduced by the use of getitem for repetition,
  overlooking Python's legacy implementation of iteration
  by sequentially calling getitem with increasing numbers until
  getting an IndexError. Found during investigation of problem
  reported by murlock, merci!

Version 2.4.2a1 - July, 2019

It turns out I got the meaning of [...] absolutely backwards,
so I've deleted 2.4.1 and am repushing this release as 2.4.2a1
for people to give it a try before I can call it ready to go.

The expr[...] notation was pushed out to be synonymous with
OneOrMore(expr), but this is really counter to most Python
notations (and even other internal pyparsing notations as well).
It should have been defined to be equivalent to ZeroOrMore(expr).

• Changed [...] to emit ZeroOrMore instead of OneOrMore.

... (truncated)

Commits

• bc531f1 Include new files filetypes and dirs in MANIFEST.in
• a94746d Update README to include links to online docs - also remove numerous special ...
• 310639e Updates to prep for 2.4.2 release
• 8d6a132 Fold in 2.4.1.1 blurb from 2.4.1.x branch, describing known issues in 2.4.1.1
• 1c1405d Add unit test for #103; also make CHANGES blurb and HowToUse notes a little c...
• 7eb54f0 More accurate description of bugs and their respective fixes
• c1a136d Fixed faux iteration behavior implicit with using getitem, found while in...
• 9f9ec78 Merge branch 'pyparsing_2.4.x'
• a64494d Version 2.4.2a1 - changing [...] notation to ZeroOrMore, not OneOrMore
• 1363860 Update version in prep for new 2.5.x work
• 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it). To ignore the version in this PR you can just close it
• @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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #12.