Build: Bump pyparsing from 3.3.2 to 3.3.3

[dependabot]

Bumps pyparsing from 3.3.2 to 3.3.3.

Changelog

Sourced from pyparsing's changelog.

Version 3.3.3 - in development

• Added support for Python 3.15.

• Parse actions that return a tuple value for a named expression formerly saved just the first value of the tuple. Now they return the entire tuple. Partially fixes Issue #401, PR #640 submitted by Vincent Gao et AI.

• Fixed CI unit test jobs selecting a tox environment with no test commands. The matrix and fallback now select py-unit, as diagnosed and proposed by glaziermag in issue #662; submitted by Neal Lin et AI.

• Fixed Dict returning an empty nested ParseResults.as_dict() as [] instead of {}. Incorporates partial solution submitted in PR #635 submitted by Leo Ji.

  Additional fixes found as part of this work:

  • Removed vestigial unused ParseResults._modal attribute.

  • Fixed incidental bug when Dict tries to create a dict with a ParseResults value for a key (not hashable).

• Fixed Word(..., max=n) raising instead of matching up to max characters when the character set contained whitespace - Word(nums, max=3) and Word(nums + " ", max=3) gave opposite results on the same input. Now both forms match up to max and leave the rest for the next parser. PR #646 submitted by Andrew Chen et AI.

• Fixed QuotedString stripping whitespace that is part of a multi-character quote delimiter, e.g. the leading newline in QuotedString("\n;", multiline=True). The delimiter was silently collapsed to ";", so the newline was ignored when matching. QuotedString now only rejects quote_char/end_quote_char values that are empty or entirely whitespace, and preserves any surrounding whitespace that is part of a valid delimiter. Reported in issue #492.

• Fixed pyparsing_common.as_datetime raising Invalid date/time: microsecond must be in 0..999999 for valid ISO-8601 timestamps whose fractional seconds round up to a full second (e.g. 2021-06-15T12:30:59.9999995, common in nanosecond-precision timestamps). The rounded microseconds are now added via timedelta so the value carries into the next second instead of overflowing the datetime microsecond argument. PR submitted by Andrew Chen et AI.

• Fixed debug output corruption when a parsed line contains a carriage return or other control character. set_debug() printed the source line verbatim, so a stray \r returned the terminal cursor to column 0 and overwrote the "Match ... at loc" text. Control characters in the debug line are now shown escaped, and the marker caret stays aligned with the match location. Issue #496, reported by Matthew Rowles.

... (truncated)

Commits

• d90d38b Update flit version and exclusion of generated railroad diagrams from source ...
• 4220992 Updated CI to execute unit tests, PR #663; update test_unit.py to add test ca...
• e266043 Reworked internal recursive implementations to use local stack vars or iterat...
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[ebyhr]

______________________________ test_with_function ______________________________

    def test_with_function() -> None:
        with pytest.raises(ParseException) as exc_info:
            parser.parse("foo = 1 and lower(bar) = '2'")
    
>       assert "Expected end of text, found 'and'" in str(exc_info)
E       assert "Expected end of text, found 'and'" in '<ExceptionInfo Expected {{{W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in \'"\'} [. {W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in \'"\'}]...}]... \'not\' \'like\' string enclosed in single quotes} | \'true\' | \'false\'}, found \'lower\'  (at char 12), (line:1, col:13) tblen=3>'
E        +  where '<ExceptionInfo Expected {{{W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in \'"\'} [. {W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in \'"\'}]...}]... \'not\' \'like\' string enclosed in single quotes} | \'true\' | \'false\'}, found \'lower\'  (at char 12), (line:1, col:13) tblen=3>' = str(<ExceptionInfo Expected {{{W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in '"'} [. {W:(A-Z_a-z, $0-9A-Z_a-z) | string enclosed in '"'}]...}]... 'not' 'like' string enclosed in single quotes} | 'true' | 'false'}, found 'lower'  (at char 12), (line:1, col:13) tblen=3>)

tests/expressions/test_parser.py:223: AssertionError

[Fokko]

Yes, this is the reason why we have dependabot. Pyparsing is known for breaking stuff. Maybe we can check if we can change the code in such a way that it works for 3.3.2 and 3.3.3

[sanjana459]

@Fokko I looked into these two failures. pyparsing 3.3.3 replaced infix_notation with a new iterative implementation, and when an operand fails to parse it drops that error and raises a new one at the start of the operand. So it's not only the test wording: on 3.3.3 a bad row filter like foo = used to report Expected ... (at char 6) and now reports a grammar dump at char 0. Upstream has a related open regression (pyparsing/pyparsing#672); a 3.3.4 was mentioned but hasn't been released.

Two options that work on both 3.3.2 and 3.3.3:

1. Write the NOT/AND/OR precedence explicitly with a Forward instead of infix_notation (~10 lines). The existing tests pass unchanged on both versions, and on 10k random filters it gave the same results and error positions as the current grammar. Trade-off: it doesn't get 3.3.3's support for very deeply nested parentheses.
2. Keep infix_notation, name the predicate so the 3.3.3 message is readable, and relax the two assertions. Smaller, but error positions on 3.3.3 still point at the start of the operand.

I'd lean toward 1. Happy to open a PR for whichever you prefer.

[sanjana459]

Small follow-up after looking at the commits on this branch: the test module currently fails to import (NameError: name 'BooleanExpression' is not defined, it's still used by test_boolean_as_operand), which is why CI is red. With the import restored, the updated assertions pass on 3.3.3 but fail on 3.3.2, since they match 3.3.3's new message (including the char-0 position). Either option above would make it pass on both.