Skip to content

Bump pyparsing from 2.4.7 to 3.0.3

Dariush Mohandesrequested to merge
dependabot/pip/pyparsing-3.0.3 into master

Created by: dependabot[bot]

Bumps pyparsing from 2.4.7 to 3.0.3.

Release notes

Sourced from pyparsing's releases.

pyparsing 3.0.3

  • Fixed regex typo in one_of fix for as_keyword=True.

  • Fixed a whitespace-skipping bug, Issue #319, introduced as part of the revert of the LineStart changes. Reported by Marc-Alexandre Côté, thanks!

  • Added header column labeling > 100 in with_line_numbers - some input lines are longer than others.

pyparsing 3.0.2

  • Reverted change in behavior with LineStart and StringStart, which changed the interpretation of when and how LineStart and StringStart should match when a line starts with spaces. In 3.0.0, the xxxStart expressions were not really treated like expressions in their own right, but as modifiers to the following expression when used like LineStart() + expr, so that if there were whitespace on the line before expr (which would match in versions prior to 3.0.0), the match would fail.

    3.0.0 implemented this by automatically promoting LineStart() + expr to AtLineStart(expr), which broke existing parsers that did not expect expr to necessarily be right at the start of the line, but only be the first token found on the line. This was reported as a regression in Issue #317.

    In 3.0.2, pyparsing reverts to the previous behavior, but will retain the new AtLineStart and AtStringStart expression classes, so that parsers can chose whichever behavior applies in their specific instance. Specifically:

    # matches expr if it is the first token on the line (allows for leading whitespace)
LineStart() + expr
matches only if expr is found in column 1
AtLineStart(expr)

  • Performance enhancement to one_of to always generate an internal Regex, even if caseless or as_keyword args are given as True (unless explicitly disabled by passing use_regex=False).

  • IndentedBlock class now works with recursive flag. By default, the results parsed by an IndentedBlock are grouped. This can be disabled by constructing the IndentedBlock with grouped=False.

pyparsing 3.0.1

  • Fixed bug where Word(max=n) did not match word groups less than length 'n'. Thanks to Joachim Metz for catching this!

  • Fixed bug where ParseResults accidentally created recursive contents. Joachim Metz on this one also!

  • Fixed bug where warn_on_multiple_string_args_to_oneof warning is raised even when not enabled.

pyparsing 3.0.0

Version 3.0.0 -

Version 3.0.0.final -

  • Added support for python -W warning option to call enable_all_warnings() at startup. Also detects setting of PYPARSINGENABLEALLWARNINGS environment variable to any non-blank value.

  • Fixed named results returned by url to match fields as they would be parsed using urllib.parse.urlparse.

  • Early response to with_line_numbers was positive, with some requested enhancements: . added a trailing "|" at the end of each line (to show presence of trailing spaces); can be customized using eol_mark argument . added expand_tabs argument, to control calling str.expandtabs (defaults to True to match parseString) . added mark_spaces argument to support display of a printing character in place of spaces, or Unicode symbols for space and tab characters . added mark_control argument to support highlighting of control characters using '.' or Unicode symbols, such as "␍" and "␊".

... (truncated)

Changelog

Sourced from pyparsing's changelog.

Version 3.0.3 -

  • Fixed regex typo in one_of fix for as_keyword=True.

  • Fixed a whitespace-skipping bug, Issue #319, introduced as part of the revert of the LineStart changes. Reported by Marc-Alexandre Côté, thanks!

  • Added header column labeling > 100 in with_line_numbers - some input lines are longer than others.

Version 3.0.2 -

  • Reverted change in behavior with LineStart and StringStart, which changed the interpretation of when and how LineStart and StringStart should match when a line starts with spaces. In 3.0.0, the xxxStart expressions were not really treated like expressions in their own right, but as modifiers to the following expression when used like LineStart() + expr, so that if there were whitespace on the line before expr (which would match in versions prior to 3.0.0), the match would fail.

    3.0.0 implemented this by automatically promoting LineStart() + expr to AtLineStart(expr), which broke existing parsers that did not expect expr to necessarily be right at the start of the line, but only be the first token found on the line. This was reported as a regression in Issue #317.

    In 3.0.2, pyparsing reverts to the previous behavior, but will retain the new AtLineStart and AtStringStart expression classes, so that parsers can chose whichever behavior applies in their specific instance. Specifically:

    # matches expr if it is the first token on the line
# (allows for leading whitespace)
LineStart() + expr
matches only if expr is found in column 1
AtLineStart(expr)

  • Performance enhancement to one_of to always generate an internal Regex, even if caseless or as_keyword args are given as True (unless explicitly disabled by passing use_regex=False).

  • IndentedBlock class now works with recursive flag. By default, the results parsed by an IndentedBlock are grouped. This can be disabled by constructing the IndentedBlock with grouped=False.

Version 3.0.1 -

  • Fixed bug where Word(max=n) did not match word groups less than length 'n'.

... (truncated)

Commits
  • bf17712 Update version time
  • b7f7f58 Added header column labeling > 100 in with_line_numbers
  • 1bbc832 Fix whitespace skipping bug introduced while reverting LineStart() changes - ...
  • 46f4af6 Fix regex typo in one_of (:? should be (?:
  • c218b88 Update version for next release
  • 6f13940 Update docs to reflect reverting LineStart and StringStart changes made in 3.0.0
  • 280f71a Fixed type annotation in IndentedBlock
  • 1be3b53 Fixed IndentedBlock
  • 4ab17bb Revert strict LineStart interpretation in 3.0.0 to 2.4.x behavior (Issue #317)
  • 8b3d958 To blacken
  • 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)

Merge request reports