Support Py3.12 in tests by constraining pyproj in lockfile to versions with wheels #745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds environment markers to the
uv
tooling configuration constraint-dependencies forpyproj
, allowing us to have a lockfile withpyproj
wheels for Python versions we support without restricting versions for downstream consumers.I believe the path to supporting 3.13 in tests will require updating
fiona<1.10
to something likefiona>1,<=1.10
. It also looks safe to bump DuckDB in our lockfile but we will have to invalidate the CI cache so it doesn't point to extensions compiled for1.1.3