Skip to content

Conversation

@rettinghaus
Copy link
Contributor

Using newer versions of pyparsing throws several deprecation warnings.
I set the minimal version for pyparsing to 3.0.0 and updated it's usage to silence the warnings and keep it future proof.

@aweakley aweakley requested review from aweakley and cameron-simpson and removed request for aweakley January 9, 2026 00:33
@aweakley
Copy link
Member

aweakley commented Jan 9, 2026

@cameron-simpson please could you review this one? If we're introducing a new minimum version of pyparsing, I think we should increment our version number?

@cameron-simpson
Copy link
Collaborator

This looks good to me.
I don't think this introduces any breaking changes or new features, so I would expect to bump the release to just 5.0.1.
The new >=3.0.0 should ensure a smooth update for end users.

@cameron-simpson
Copy link
Collaborator

If we're introducing a new minimum version of pyparsing, I think we should increment our version number?

I think just 5.0.1 for the next release.

I'd just merge this unless there's some "prospective next release" field I need to be updating?

@aweakley
Copy link
Member

aweakley commented Jan 9, 2026

Ok great, thank you I'll merge it. Thanks very much @rettinghaus

@aweakley aweakley merged commit 54a9b47 into ixc:main Jan 9, 2026
0 of 9 checks passed
@rettinghaus rettinghaus deleted the fix/warnings branch January 9, 2026 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants