Diagnose Shebang Virtualenv Import Errors

Debugging pattern for ModuleNotFoundError when CLI entry points use wrong Python interpreter

vamseeachanta 8e2d57a 720 B Updated

File contents

Diagnose Shebang vs Virtual Environment Import Errors

When a CLI tool installed in a venv throws ModuleNotFoundError for packages that exist in that venv, check if the entry point shebang uses the system Python instead of the venv Python. Verify the actual shebang in ~/.local/bin/, check which python it resolves to with which python3, and compare against the venv's bin/python3 path. If mismatched, update the shebang to point directly to the venv interpreter. Note: this can revert on tool updates if the installer regenerates the entry point.

vamseeachanta/workspace-hub/tree/main/.agents/skills/workspace-hub/learned/diagnose-shebang-virtualenv-import-errors commit 8e2d57a062

Frequently asked questions

npx skillmds@latest add vamseeachanta/diagnose-shebang-virtualenv-import-errors