Python virtualenvs/Poetry

[tiagoantao]

Hi,

I have started to use Zed and I am finding an ergonomics problem with Python (Poetrry/virtualenvs).

When I have a project, Zed doesn't automatically find the virtual env / poetry install for the project. Which means that the editor is not able to resolve dependencies for packages used in the project.

I have found a couple of answers here, but they require adding a configuration file for pyright - which is very ugly compared to all other editors...

... It so happens that other editors don't require that (and adding a configuration file for a pyright environment would cause problems for other collaborators).

For example with vim I do:

poetry shell
vim blah.py # all fine here

Because vim is run inside the virtual environment the problem is automatically solved. The impression that I have is that other editors are able to solved this problem in whatever way.

Any ideas on how to solve this elegantly (i.e. this is automaticallly solved without adding pyright configuration directives)?

Thanks

[hongquan]

This is not a direct answer, but, when adding pyright configuration, you should use pyrightconfig.json file and make it ignored by Git, to let other collaborators use their own content.

[tiagoantao]

I get that and it works (thanks!), but with other editors this step is not needed. Either because you are inside the enviroment (e.g. with vim) or because they have ways to resolve it

[hongquan]

Agree. This should be supported by Zed, because which Python venv is active also affects other features/tools, not just PyRight.

[pjv]

I do not use poetry so this is not really an answer in that context and I agree 100% that it would be great to make Zed’s detection of python virtual environments more comprehensive, hands-off, and bullet-proof.

In the mean time, what I’ve done is configure things in my setup (where I use pyenv and direnv to create python projects) so that my virtual environment python install (regardless of what python version a given venv is using) will always be located under .venv in the project’s directory.

And then I have the following in my zed settings.json:

 "lsp": {
   "basedpyright": {
       "python": {
         "pythonPath": ".venv/bin/python"
       }
     }
   },
   "pyright": {
     "settings": {
       "python": {
         "pythonPath": ".venv/bin/python"
       }
     }
   },
…

In this way, these python LSP’s find the venv in every project without requiring a pyrightconfig.json in that project’s directory.

[hanxuanliang]

https://www.reddit.com/r/ZedEditor/comments/1cth023/cant_get_zed_to_recognize_any_python_libraries/

It seems this approach can solve the current problem, but Zed is still not smart enough.

[trieungoctam]

In pyproject.toml:

[tool.pyright]
venvPath = "."
venv = ".venv"

pyright will look for the virtual environment in the project. Next, we need to configure poetry to create the virtual environment in the project:

poetry config virtualenvs.in-project true

[hongquan]

Note that, not all developers want to keep virtual env in the same project folder, and adding this configuration to pyproject.toml, which is tracked by Git, will stop teammates from using their own virtual environment.