From 751576ee94accbc9ee64415bc5c512597b982f3f Mon Sep 17 00:00:00 2001 From: Berk Geveci Date: Thu, 17 Sep 2026 14:18:12 -0400 Subject: [PATCH] build(uv): keep the pip vtk wheel out of the dev venv trame-colormaps 1.6 depends on vtk. Under the uv dev setup that pulls the standalone pip wheel into .venv, and `pvpython --venv .venv` then finds its vtkmodules ahead of ParaView's own, which are built against ParaView's libraries -- the app dies at startup. uv.lock already carries this override, so the two have been out of step: regenerating the lock from the manifest as it stands would drop the override and reintroduce the crash. Only affects the uv path; conda installs get vtk from ParaView. --- pyproject.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pyproject.toml b/pyproject.toml index 24aaa54..e9a6482 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -55,6 +55,12 @@ quickview-chunk = "e3sm_quickview.cli.chunk:main" [project.entry-points."jupyter_serverproxy_servers"] quickview = "e3sm_quickview.jupyter:setup_quickview" +[tool.uv] +# ParaView's pvpython supplies its own vtkmodules built against its libraries. +# trame-colormaps>=1.6 pulls in the standalone pip `vtk` wheel, whose vtkmodules +# collide with ParaView's and crash the app at startup. Keep it out of the venv. +override-dependencies = ["vtk; sys_platform == 'never'"] +