Issue specifying python_interpreter

[jegork]

Currently, I have an issue specifying python_interpreter to use pyrefly in my venv
My project is managed by poetry.

If I have the following zed config

  "lsp": {
    "pyrefly": {
      "binary": {
        "path": ".venv/bin/pyrefly",
        "arguments": ["lsp"],
        "env": {
          "PYREFLY_PYTHON_INTERPRETER": ".venv/bin/python"
        }
      },
      "settings": {
        "python": {
          "pythonPath": ".venv/bin/python"
        },
        "pyrefly": {
          "python_interpreter": ".venv/bin/python"
        }
      }
    }

I get the following error highlighted on my imports

Could not find import of `sqlalchemy.ext.asyncio`, looked in these locations (from config in `/Users/jegorkitskerkin/Documents/projects/cynthai-backend/pyproject.toml`):
Import root (inferred from project layout): "/Users/jegorkitskerkin/Documents/projects/cynthai-backend"
Site package path (queried from interpreter at `/Users/jegorkitskerkin/.local/bin/python3`): ["/Users/jegorkitskerkin/.local/share/uv/python/cpython-3.13.3-macos-aarch64-none/lib/python3.13", "/Users/jegorkitskerkin/.local/share/uv/python/cpython-3.13.3-macos-aarch64-none/lib/python3.13/lib-dynload", "/Users/jegorkitskerkin/.local/share/uv/python/cpython-3.13.3-macos-aarch64-none/lib/python3.13/site-packages"] (Pyrefly import-error)

You can see that even though python_interpreter and the env variable are set, it still queries the system wide python interpreter.

However, the issue is fixed if I specify in my pyproject.toml

[tool.pyrefly]
python_interpreter = ".venv/bin/python"

could it be linked to?

• Pyrefly Cannot Correctly Figure Out Dependencies in Non-VSCode Editors facebook/pyrefly#356
• How does Pyrefly expect the interpreter be passed to it via LSP? facebook/pyrefly#221

[connernilsen]

Hey @jegork, quick question, if you set PYREFLY_PYTHON_INTERPRETER to an absolute path to the interpreter, does that work for you? I'm wondering if the cwd of zed is causing Pyrefly to rewrite the path to something that doesn't exist.

Also, are there any other Pyrefly logs going on that seem useful here?

[jegork]

hey @connernilsen
tried providing absolute path both for the env variable and/or pyrefly.settings.pyrefly.python_interpreter -- no luck!

After you mentioned the logs, it seems that the env is not being set?

2025-06-06T11:33:47+03:00 INFO  [lsp] starting language server process. binary path: "/Users/jegorkitskerkin/.local/bin/pyrefly", working directory: "/Users/jegorkitskerkin/Documents/projects/cynthai-ml-models", args: ["lsp"]

[connernilsen]

I just landed facebook/pyrefly#451, which might help fix this. We weren't performing searching logic for .venvs when running in LSP mode, since we incorrectly assumed it would always be provided by the IDE. Now we handle that correctly, and it will be released soon (likely before next week, if I can get some other functionality landed I want to go out soon)!

I also noticed recently that our logging around when an interpreter is found was a little off/misleading. I landed facebook/pyrefly#450, and I have facebook/pyrefly#470 ready to go too.

c.c. @grievejia who was also looking at this/had an issue with Zed

[connernilsen]

@jegork Alright, just released 0.19.1, which should fix this issue. Try it out when you get a chance, and let me know if it's working for you!