From d0dcb7fc637f8e28b2d9fabadf08fd275f50c02b Mon Sep 17 00:00:00 2001 From: HerenderKumar Date: Tue, 21 Jul 2026 10:47:47 +0530 Subject: [PATCH] docs(readme): troubleshoot an older graphifyy shadowing `uv run` (#1540) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `uv run --with graphifyy python -m graphify` runs the system interpreter, so an older `graphifyy` in system site-packages loads before the uv-managed one — with no error. Env overrides like OPENAI_BASE_URL are then ignored and requests 401 against the default endpoint. The existing `skill is from graphify X, package is Y` warning is the real fingerprint, but users dismiss it as a stale skill. Add a troubleshooting entry next to the uvx-resolution one: name the symptom, show how to confirm which module actually loaded, and point at `uvx --from graphifyy` / uninstalling the stale copy. --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 792d9622b..90ed2105c 100644 --- a/README.md +++ b/README.md @@ -550,6 +550,17 @@ The CLI is installed but its bin directory isn't on your shell's `PATH`. Pick th **`uvx graphify …` or `uv tool run graphify …` fails to resolve `graphify`** The PyPI package is `graphifyy`; `graphify` is only the command it provides. `uv tool run` treats the first word as a *package name*, so it looks for a package called `graphify` and reports `No solution found … no versions of graphify`. Name the package explicitly: `uvx --from graphifyy graphify install` (same as `uv tool run --from graphifyy graphify install`). Or `uv tool install graphifyy` once and then call `graphify` directly. +**`uv run --with graphifyy python -m graphify` silently runs an older install** +`uv run` uses your *system* Python, so if an older `graphifyy` also lives there (e.g. a past `pip install graphifyy`), Python can find that copy first on `sys.path` and `--with graphifyy` won't override it. It runs with no error, but you get the *old* version's behavior — e.g. env overrides like `OPENAI_BASE_URL` are silently ignored, so requests hit the default endpoint and fail with a 401 that looks like a bad key. The fingerprint is a `warning: skill is from graphify , package is ` line — that means a different install was loaded, not just a stale skill. Check which copy actually loaded: +```bash +python -c "import graphify; print(graphify.__file__)" +``` +Then run the installed command directly (it uses the uv-managed copy), or drop the stale system copy: +```bash +uvx --from graphifyy graphify extract . --backend openai # names the package explicitly +pip uninstall graphifyy # or remove the old system install +``` + **`python -m graphify` works but `graphify` command doesn't** Your shell's `PATH` doesn't include the bin directory the command was installed to. Prefer `uv tool install` / `pipx install` over plain `pip`, then run `uv tool update-shell` / `pipx ensurepath` and open a new terminal (see the install notes above).