Fixing VSCode Extension Using the Wrong python Interpreter for sqlfluff

Learn how to resolve VSCode using an unintended Python version for the sqlfluff linter by configuring environment variables properly.
---
This video is based on the question https://stackoverflow.com/q/79376992/ asked by the user 'Nir' ( https://stackoverflow.com/u/719001/ ) and on the answer https://stackoverflow.com/a/79377457/ provided by the user 'Nir' ( https://stackoverflow.com/u/719001/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: vscode extension uses wrong python

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to drop me a comment under this video.
---
The Problem: VSCode Uses Wrong Python Interpreter for sqlfluff

When using the sqlfluff SQL formatter and linter extension in Visual Studio Code (VSCode) on macOS, you might encounter an error indicating that sqlfluff is running under a different Python version than expected. For example, the extension may use Python 3.11 from Homebrew (/opt/homebrew/lib/python3.11) instead of your preferred Python 3.12 installation located at /Library/Frameworks/Python.framework/Versions/3.12/bin/python3.12.

Even if your terminal's python command points to the correct version and you have set the interpreter in VSCode (Python: Select Interpreter), the extension can still default to another Python environment for running sqlfluff.



Understanding the Root Cause

The extension's subprocess may inherit environment variables different from your terminal's.

sqlfluff found in /opt/homebrew/bin/sqlfluff is likely installed via Homebrew and is tied to its own Python environment (here, Python 3.11).

VSCode does not automatically align the extension’s environment with the selected Python interpreter.



Simple Solution: Set PATH Explicitly in VSCode Settings

You can resolve this by explicitly setting the PATH environment variable for the sqlfluff extension in your VSCode settings.json:

[[See Video to Reveal this Text or Code Snippet]]

Explanation:

This prepends the correct Python 3.12 binary path to the PATH, ensuring sqlfluff runs with the desired Python environment.

The ${env:PATH} keeps the existing system path intact.

Why This Works:

The extension runs sqlfluff commands based on the PATH it uses.

Adjusting the environment variables within VSCode ensures consistency between your Python interpreter and sqlfluff runtime.



Additional Recommendations

Avoid multiple conflicting Python installations when possible.

Use Python virtual environments to isolate package versions, and point VSCode to the virtual environment interpreter.

Reinstall sqlfluff inside your virtual environment rather than relying on globally installed versions (like Homebrew’s).



Summary

If sqlfluff in VSCode uses an unwanted Python version:

Check which sqlfluff executable is being run (which sqlfluff).

Configure the extension's environment variables to specify the correct Python path.

Update settings.json with the appropriate PATH variable under sqlfluff.env.environmentVariables.

This will ensure consistent, expected behavior when formatting or linting SQL files.