Support Py3.12 in tests by constraining pyproj in lockfile to version…

…s with wheels (#745)

This PR adds environment markers to the `uv` tooling configuration
[constraint-dependencies](https://docs.astral.sh/uv/reference/settings/#constraint-dependencies)
for `pyproj`, allowing us to have a lockfile with `pyproj` 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 like `fiona>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 for `1.1.3`

.github/workflows/test.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: [3.9, "3.10", "3.11"]
+        python-version: [3.9, "3.10", "3.11", "3.12"]
 
     steps:
       - uses: actions/checkout@v4

pyproject.toml

@@ -126,3 +126,10 @@ select = [
 "__init__.py" = [
     "F401", # Allow unused imports in __init__.py files
 ]
+
+[tool.uv]
+constraint-dependencies = [
+    # ensure lockfile grabs wheels for pyproj for each Python version
+    "pyproj==3.6; python_version == '3.9'",
+    "pyproj>=3.7; python_version >= '3.10'",
+]