Diagnose Shebang Venv Import Errors

Troubleshoot ModuleNotFoundError in CLI tools by identifying shebang-venv mismatches

vamseeachanta Updated

File contents

Diagnose Shebang vs Virtual Environment Import Errors

When a CLI tool fails with ModuleNotFoundError despite the package being installed, check if the shebang in /usr/local/bin/ or ~/.local/bin/ points to system Python instead of the venv Python. Verify the actual Python interpreter being used by examining the shebang (#!/usr/bin/env python3 vs /path/to/venv/bin/python3). If mismatched, update the shebang to explicitly point to the venv's Python executable. Be aware that auto-update mechanisms may revert custom shebangs—check for post-install scripts that regenerate entry points.

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

Frequently asked questions

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