Update pyparsing requirement from >=3.0,<=3.1.1 to >=3.1,<4.0

[dependabot]

Bumps pyparsing from 3.1.1 to 3.3.2.

Changelog

Sourced from pyparsing's changelog.

Version 3.3.2 - January, 2026

• Defined pyparsing-specific warning classes so that they can be selectively enabled or disabled without affecting warnings raised by other libraries in the same Python app:

  • PyparsingWarning - base warning for all pyparsing-specific warnings (inherits from UserWarning)
  • PyparsingDeprecationWarning - warning for using deprecated features (inherits from PyparsingWarning and DeprecationWarning)
  • PyparsingDiagnosticWarning - warning raised when pyparsing diagnostics are enabled and a diagnostic feature is used (inherits from PyparsingWarning)

• Added as_datetime parse action to pyparsing.common - a more generalized version of the convert_to_datetime parse action (supports any expression that extracts date/time fields into "year", "month", "day", etc. results names), and validates that the parsed fields represent a valid date and time.

• Added iso8601_date_validated and iso8601_datetime_validated expressions to pyparsing.common, which return a Python datetime.datetime

• Various performance improvements in ParseResults class and core functions, with 10-20% performance overall.

• Added regex_inverter web page (using PyScript) to demonstrate using the inv_regex.py example.

• Expanded regex forms handled by the examples/inv_regex.py example:

  • named capturing groups (?P<name>)
  • partial repetition ({m,} and {,n})
  • negated character classes ([^...])

• Added SPy (Simplified Python) parser to examples.

Version 3.3.1 - December, 2025

• Added license info to metadata, following PEP-639. Thanks to Gedalia Pasternak and Marc Mueller for submitted issue and PR. Fixes #626.

Version 3.3.0 - December, 2025

=========================================================================================== The version 3.3.0 release will begin emitting DeprecationWarnings for pyparsing methods that have been renamed to PEP8-compliant names (introduced in pyparsing 3.0.0, in August, 2021, with legacy names retained as aliases). In preparation, I added in pyparsing 3.2.2 a utility for finding and replacing the legacy method names with the new names. This utility is located at pyparsing/tools/cvt_pep8_names.py. This script will scan all Python files specified on the command line, and if the -u option is selected, will replace all occurrences of the old method names with the new PEP8-compliant names,

... (truncated)

Commits

• fa24016 Sync regex_inverter example from pyparsing
• ea22046 Updates to regex_inverter example: handle cancel during long max_results inte...
• 7df5c09 Sync regex_inverter example from pyparsing
• e862afa Add Regular Expressions Quick Reference to regex_inverter/index.html
• 6fdbd88 Sync regex_inverter example from pyparsing
• 5b33045 Add note in the regex inverter that only the 7-bit ASCII characters are used ...
• e403f2c Merge branch 'master' of https://github.com/pyparsing/pyparsing
• e7b5f1c Fix repo sync action in sync-regex-inverter.yml
• ea463fa Sync regex_inverter example from pyparsing
• afcbdac Change repetition instructions to use {,4} instead of {,10}
• 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 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)

[fhightower]

Review Summary

Dependency type: Non-dev / production (listed under [project] dependencies in pyproject.toml)

CI status: All checks were failing due to uv.lock being out of date (--locked flag). Fixed by running uv lock.

Changelog findings (pyparsing 3.1.1 → 3.3.2):

• 3.2.0: Dropped Python 3.6-3.8 (not relevant). Possible breaking changes in ParseElementEnhance exception handling, transform_string() whitespace preservation, and IndexError in parse actions.
• 3.3.0: Begins emitting DeprecationWarning for legacy non-PEP8 method names. ioc-finder uses addCondition, searchString, and parseString throughout — these still work but will now emit warnings. A migration tool is provided at pyparsing/tools/cvt_pep8_names.py. Consider migrating to PEP8 names (add_condition, search_string, parse_string) in a follow-up.
• 3.3.1-3.3.2: Minor fixes and performance improvements.

Version range adjustment:

• Dependabot proposed: >=3.0,<=3.3.2
• Applied (non-dev slide rule adapted for minor versions): >=3.1,<4.0

🤖 Generated with Claude Code

[fhightower]

Superseded by #321 which consolidates all pending dependency updates.

[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.