Skip to content

Conversation

stefanvanburen
Copy link
Member

We implemented this so that we could avoid a hard dependency on google/re2 due to the lack of wheels being published for Python 3.13. However, 3.13 wheels are now published, and our downstream cel-python dep, as of v0.4, is requiring google/re2 as a dependency. It seems like we ought to remove our matches workaround, as well as the configuration for supplying a user-defined matching func, as we generally want all users to have the same behavior for matching. (We can keep in the config value if we really think it's necessary.)

We implemented this so that we could avoid a hard dependency on
google/re2 due to the lack of wheels being published for Python
3.13. However, [3.13 wheels are now published][1], and our downstream
cel-python dep, as of v0.4, is requiring google/re2 as a dependency. It
seems like we ought to remove our matches workaround, as well as the
configuration for supplying a user-defined matching func, as we
generally want all users to have the same behavior for matching. (We can
keep in the config value if we really think it's necessary.)

[1]: google/re2#516
@stefanvanburen stefanvanburen requested a review from smaye81 July 28, 2025 17:24
@stefanvanburen stefanvanburen marked this pull request as ready for review July 28, 2025 17:24
@chrispine
Copy link

no need to keep it in the config

@stefanvanburen stefanvanburen merged commit caae239 into main Jul 28, 2025
13 checks passed
@stefanvanburen stefanvanburen deleted the svanburen/drop-custom-matcher branch July 28, 2025 18:38
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