Skip to content

Conversation

stefanvanburen
Copy link
Member

Closes #380. To be merged at the end of the month.

via:

```console
uvx pyupgrade --py310-plus protovalidate/**.py test/**.py
```
Even though this is asserted above, we ought to keep this check around.
```console
$ uv run ruff check --fix --unsafe-fixes protovalidate/ test/
```
stefanvanburen added a commit that referenced this pull request Oct 8, 2025
This reverts commit fb15875.

When working through #384 without a pin set, running `make` would
default to Python 3.13 locally. (Not sure if this is a `uv` version
thing, or what.)

 I think it's best to keep this pinned in Python libraries to the lowest
 supported Python version to avoid confusion, especially since we don't
 specify a `uv` version to use (for now).
stefanvanburen added a commit that referenced this pull request Oct 8, 2025
This reverts commit fb15875.

When working through #384 without a pin set, running `make` would
default to Python 3.13 locally. (Not sure if this is a `uv` version
thing, or what.)

I think it's best to keep this pinned in Python libraries to the lowest
supported Python version to avoid confusion, especially since we don't
specify a `uv` version to use (for now).
stefanvanburen added a commit that referenced this pull request Oct 9, 2025
…385)

This reverts commit fb15875.

When working through #384 without a pin set, running `make` would
default to Python 3.13 locally. (Not sure if this is a `uv` version
thing, or what.)

I think it's best to keep this pinned in Python libraries to the lowest
supported Python version to avoid confusion, especially since we don't
specify a `uv` version to use (for now).
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.

Drop Python 3.9 official support

1 participant