chore(deps): update dependency pyparsing to v3.3.2

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
pyparsing	==3.2.5 → ==3.3.2

---

Release Notes

pyparsing/pyparsing (pyparsing)

v3.3.2

Compare Source

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

v3.3.1

Compare Source

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

v3.3.0

Compare Source

===========================================================================================
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,
updating the files in place.

Here is an example that converts all the files in the pyparsing /examples directory:

  python -m pyparsing.tools.cvt_pyparsing_pep8_names -u examples/*.py

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the pyparsing dependency to its latest version, 3.3.2. This update brings several enhancements, including new warning classes for better error handling, improved date/time parsing capabilities, and significant performance optimizations. It also incorporates changes that prepare for future deprecations by introducing a utility for method name conversion, ensuring the project benefits from the latest features and stability improvements in the pyparsing library.

Highlights

• Dependency Update: The pyparsing dependency has been updated from version 3.2.5 to 3.3.2.
• New Warning Classes: Pyparsing-specific warning classes (PyparsingWarning, PyparsingDeprecationWarning, PyparsingDiagnosticWarning) were introduced for better warning management.
• Date/Time Parsing Enhancements: New as_datetime parse action and iso8601_date_validated, iso8601_datetime_validated expressions were added for more robust date and time parsing.
• Performance Improvements: Various performance improvements, resulting in a 10-20% overall speedup, were implemented in the ParseResults class and core functions.
• Deprecation Handling: Version 3.3.0 begins emitting DeprecationWarnings for renamed methods, and a utility (cvt_pep8_names.py) is available to assist with converting legacy method names to PEP8-compliant ones.

Changelog

• requirements.txt
  • Updated pyparsing from 3.2.5 to 3.3.2 and refreshed its SHA256 hashes.

Activity

• This pull request was automatically generated by Renovate Bot to update the pyparsing dependency.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the pyparsing dependency from version 3.2.5 to 3.3.2. This update brings performance improvements and new warning classes. It is important to note that pyparsing versions 3.3.0 and above will emit DeprecationWarnings for non-PEP8 compliant method names. Please ensure that the project's code base is compatible with these changes and consider updating any legacy API calls to their PEP8-compliant equivalents to avoid future warnings.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The update to pyparsing==3.3.2 includes changes from v3.3.0 where DeprecationWarnings are now emitted for non-PEP8 compliant method names. While this is a minor version bump, it's important to check if any existing code uses these deprecated names. The pyparsing release notes mention a utility (pyparsing.tools.cvt_pyparsing_pep8_names.py) that can help in migrating to the new names, which would be beneficial for long-term maintainability and to prevent warnings in logs.