Question 1

How do I show the current Python environment in my Neovim status line with swenv.nvim?

Accepted Answer

Use the built-in lualine component by adding 'swenv' to your lualine sections in configuration. You can customize the icon and color, and conditionally show it for Python file types using a cond function, as detailed in the README.

Question 2

Does swenv.nvim work with Conda environments?

Accepted Answer

swenv.nvim primarily supports standard Python virtual environments (venv) and pdm. For Conda environments, you might need to ensure they are structured like venvs or use additional configuration, as it's not explicitly supported out of the box and may not be detected by auto-features.

Question 3

How to automatically create a virtual environment from a pyproject.toml file?

Accepted Answer

Enable auto_create_venv in the setup, and swenv.nvim will search for pyproject.toml and use pip to install dependencies into a new venv directory, typically set to auto_create_venv_dir like .venv. It follows a priority order starting with pdm.lock, then requirements files.

Question 4

swenv.nvim vs venv-selector.nvim: which should I use?

Accepted Answer

swenv.nvim excels with auto-creation from dependencies and deep LSP integration, while venv-selector.nvim might focus more on selection features. Choose swenv.nvim if you need automated environment setup and minimal design, but compare based on specific plugin features and your Neovim workflow.

Question 5

Why isn't my LSP restarting after switching environments with swenv.nvim?

Accepted Answer

Ensure you have configured post_set_venv correctly to reload your LSP client. For example, with basedpyright, update the Python path settings and notify the client, as shown in the README. Check if your LSP name matches and that the configuration is applied properly.

Question 6

Can swenv.nvim detect environments automatically with project.nvim?

Accepted Answer

Yes, with project.nvim installed, swenv.nvim will automatically activate in-project venvs if present, using the project root. This integration is skipped if auto_create_venv is enabled, so configure accordingly for seamless detection.

Question 7

How to set up swenv.nvim for use with coc.nvim?

Accepted Answer

Due to loading order issues, use the timer workaround from the README: set post_set_venv to a function that checks for coc_status every 250ms and restarts Coc with vim.cmd.CocRestart once detected. This avoids failures from coc loading before environment setting.

swenv.nvim

What is swenv.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions