Skip to content

Conversation

@dependabot-preview
Copy link
Contributor

Bumps pyparsing from 2.1.10 to 2.4.4.

Release notes

Sourced from pyparsing's releases.

Pyparsing 2.4.4

Check-in bug in Pyparsing 2.4.3 that raised UserWarnings was masked by stdout buffering in unit tests - fixed.

Pyparsing 2.4.3

Version 2.4.3 - November, 2019

(Backport of selected critical items from 3.0.0 development branch.)

  • Fixed a bug in ParserElement.__eq__ that would for some parsers create a recursion error at parser definition time. Thanks to Michael Clerx for the assist. (Addresses issue #123)

  • Fixed bug in indentedBlock where a block that ended at the end of the input string could cause pyparsing to loop forever. Raised as part of discussion on StackOverflow with geckos.

  • Backports from pyparsing 3.0.0:
    . __diag__.enable_all_warnings()
    . Fixed bug in PrecededBy which caused infinite recursion, issue #127
    . support for using regex-compiled RE to construct Regex expressions

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

... (truncated)
Changelog

Sourced from pyparsing's changelog.

Version 2.4.4 - November, 2019

  • Unresolved symbol reference in 2.4.3 release was masked by stdout
    buffering in unit tests, thanks for the prompt heads-up, Ned
    Batchelder!

Version 2.4.3 - November, 2019

  • Fixed a bug in ParserElement.eq that would for some parsers
    create a recursion error at parser definition time. Thanks to
    Michael Clerx for the assist. (Addresses issue #123)

  • Fixed bug in indentedBlock where a block that ended at the end
    of the input string could cause pyaprsing to loop forever. Raised
    as part of discussion on StackOverflow with geckos.

  • Backports from pyparsing 3.0.0:
    . diag.enable_all_warnings()
    . Fixed bug in PrecededBy which caused infinite recursion, issue #127
    . support for using regex-compiled RE to construct Regex expressions

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:

... (truncated)
Commits
  • c9142bd Update CHANGES
  • fae08dc Clean up DeprecationWarnings and Py2 compat warnings
  • d78e931 Unresolved symbol reference in 2.4.3 release was masked by stdout buffering i...
  • 89be5c8 Updates for 2.4.3 release - pathlib not Py2-compatible
  • 021888d Updates for 2.4.3 release - use README.rst body instead of pyparsing docstrin...
  • e40c1df Updates for 2.4.3 release
  • 78d4be0 indentedBlock loop forever bug
  • 03f74f2 Remove reference to overriding imported re with regex module for now
  • f91b27f Backport support for 3rd party regex module
  • f5ffaa2 Backport changes from 3.0.0 to fix PrecededBy bug (Issue #127)
  • Additional commits viewable in compare view

Dependabot compatibility score

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

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Nov 6, 2019
@dependabot-preview
Copy link
Contributor Author

Superseded by #14.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/pyparsing-2.4.4 branch November 11, 2019 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant