Pipenv environments are not listed about venv-selector.nvim HOT 8 CLOSED

I removed the ~/.cache/venv-selector to fix the first problem. The second problem remains the same...

from venv-selector.nvim.

First problem is something I didn't consider actually. I think what probably happens is that the plugin is trying to activate the venv from cache, even when it's deleted, since it's still in the file that keeps track of cached venvs. We should bugfix that, thank you.

It's strange that you don't get any venvs in the telescope viewer though. Where are the poetry venvs on disk?

from venv-selector.nvim.

I added a check in the latest commit so the plugin doesnt try to activate a venv that has been deleted.

So now its a question of where your poetry venvs are and if the plugin should find them. The plugin looks in ~/Library/Caches/pypoetry/virtualenvs if you are on a Mac for example.

from venv-selector.nvim.

Hi, sorry for the delay.

• I'm on Linux, Fedora 40
• I don't use poetry, as I explained earlier I changed to pipenv and it never find any virtualenv

That worked with poetry (AFAIK), and it work with venv in the project.

from venv-selector.nvim.

Ok, thank you. And your pipenv venvs are in default locations? You are using the regexp version of the plugin?

from venv-selector.nvim.

I realized I didnt create default searches for pipenv environments in the regexp version of the plugin. Clearly an oversight and I will fix that right away...

from venv-selector.nvim.

This should be fixed now in the regexp version. Thanks for pointing this out!

from venv-selector.nvim.

Absolutely! It works now :)

from venv-selector.nvim.