Skip to content

Conversation

stefanvanburen
Copy link
Member

This reverts commit 0aedc8c.

Checked again and this should be superfluous. Removing for now.

This reverts commit 0aedc8c.

Checked again and this _should_ be superfluous. Removing for now.
@stefanvanburen stefanvanburen merged commit fb15875 into main Sep 25, 2025
13 checks passed
@stefanvanburen stefanvanburen deleted the svanburen/remove-python-version branch September 25, 2025 20:32
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.

2 participants