From a5bb4444ecb4987a4ce2b4ff72b030ce79740ab5 Mon Sep 17 00:00:00 2001 From: idatui Date: Sun, 9 Aug 2026 13:44:10 +0200 Subject: Graph: name the interpreter when pytriskel is missing ./ida-tui runs $IDATUI_PYTHON (default ~/ida-venv), which is not the repo .venv the tests use -- so the graph view can report pytriskel as missing while tests/test_graph.py is exercising both engines. "not installed" on its own sends you to check the wrong python; the status now names sys.executable, and docs/GRAPH_VIEW.md says to install into both. --- docs/GRAPH_VIEW.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/GRAPH_VIEW.md b/docs/GRAPH_VIEW.md index ea1f84d..d588b3d 100644 --- a/docs/GRAPH_VIEW.md +++ b/docs/GRAPH_VIEW.md @@ -217,10 +217,20 @@ drive raw graph action=zoom It is optional; without it everything works and `auto` means `native`. +**Install it into the interpreter the launcher actually runs**, which is +`$IDATUI_PYTHON` and defaults to `~/ida-venv/bin/python` — *not* the repo's +`.venv`, which is only what the tests use. Getting this wrong is the one way to +see `no pytriskel in ...` in the status bar while `tests/test_graph.py` happily +exercises both engines; the message names the interpreter for that reason. + ```bash -uv pip install ~/dev/triskel/bindings/python # needs cmake, ninja, a C++23 compiler +~/ida-venv/bin/python -m pip install ~/dev/triskel/bindings/python +.venv/bin/python -m pip install ~/dev/triskel/bindings/python # for the tests ``` +Needs cmake, ninja and a C++23 compiler at install time; the wheel is built from +source for whichever interpreter runs pip. + That is **our fork**, not PyPI. Upstream's wheels stop at cp313 with no sdist (so there is nothing to install on 3.14), and on any version their `get_waypoints()` raises, which means no edge routes at all. `~/dev/triskel/PATCHES.md` -- cgit v1.3.1-sl0p