Skip to content

fix(python): add ft="python" to venv-selector for auto-load on Python files - #1785

Closed
syltharion wants to merge 1 commit into
AstroNvim:mainfrom
syltharion:fix/python-venv-selector-lazy-load
Closed

syltharion wants to merge 1 commit into
AstroNvim:mainfrom
syltharion:fix/python-venv-selector-lazy-load

Conversation

@syltharion

Copy link
Copy Markdown
Contributor

Summary

Adds ft = "python" to the venv-selector.nvim plugin spec in pack.python.base so it lazy-loads when opening a Python file.

Problem

Currently venv-selector.nvim only has cmd = "VenvSelect", meaning it only loads when the user manually triggers the command. This prevents cached virtual environments from being automatically restored when opening a Python project.

Fix

Adding ft = "python" ensures the plugin loads on Python filetype detection, allowing cached venv auto-activation without manual <Leader>lv invocation.

Closes #1780

… files

Closes AstroNvim#1780

venv-selector.nvim was only configured with , meaning
it would not load when opening a Python file. This prevented cached virtual
environments from being automatically restored.

Adding  ensures the plugin loads on Python filetype detection,
allowing cached venv auto-activation without manual <Leader>lv invocation.
@github-actions

Copy link
Copy Markdown

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

  • Proper usage of opts table rather than setting things up with the config function.

  • Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

@syltharion syltharion closed this Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(python): venv-selector.nvim is not loaded on Python file open, preventing cached venv auto-activation

1 participant