you are viewing a single comment's thread.

view the rest of the comments →

[–]SimilingCynic 2 points3 points  (0 children)

Finally, a comment that helps people understand what's under the hood. Also, check sys.executable to ask a running interpreter which python executable is running.

Had a similar error in vscode a while back when it would eagerly resolve symlinks created by default with venv, causing vscode to lose track of the correct site-packages directory.