test: install DuckDB spatial extension in TestSpatial fixture

The ggsql crate only issues LOAD spatial (never INSTALL), which fails on
machines without the extension binary cached under ~/.duckdb/extensions.
CI runners start clean, so all TestSpatial tests failed on Linux/macOS
and the download attempt hung the Windows test step indefinitely.

Also add a 10-minute timeout to the test step to bound future hangs.

Author: cpsievert

.github/workflows/python.yml

@@ -76,6 +76,9 @@ jobs:
 
       - name: Run tests
         shell: bash
+        # Bound the step: a hung extension download once stalled Windows jobs
+        # indefinitely (tests themselves finish in seconds).
+        timeout-minutes: 10
         run: pytest tests/ -v
 
       # The abi3 wheel is identical across Python legs; keep just one for

tests/test_ggsql.py

@@ -220,6 +220,19 @@ def test_render_multi_layer(self):
 class TestSpatial:
     """Tests for spatial (map) layers via the VegaLiteWriter."""
 
+    @pytest.fixture(scope="class", autouse=True)
+    def install_spatial_extension(self):
+        """Install DuckDB's spatial extension (the ggsql crate only LOADs it).
+
+        The binary is cached per DuckDB version/platform under
+        ~/.duckdb/extensions, so this downloads at most once per machine.
+        """
+        reader = ggsql.DuckDBReader("duckdb://memory")
+        try:
+            reader.execute_sql("INSTALL spatial")
+        except Exception as e:
+            pytest.skip(f"DuckDB spatial extension unavailable (offline?): {e}")
+
     def test_render_spatial_builtin_world(self):
         reader = ggsql.DuckDBReader("duckdb://memory")
         spec = reader.execute("VISUALISE FROM ggsql:world DRAW spatial")