Two user-facing notifications still use the pre-:Python command names, so they tell you to run something that isn't an editor command.
lua/python/venv/detect.lua:208:
string.format("python.nvim: venv not found for '%s' run :PythonVEnvInstall to create one ", found_parent_dir),lua/python/venv/create.lua:463:
"python.nvim: Saved venv '%s' for cwd '%s'. Use :PythonVEnvDeleteSelect to remove it.",
Neither is registered. In a Python buffer with the plugin loaded, vim.api.nvim_get_commands({}) returns only Python and UV (plus unrelated ones from other plugins), and nvim_get_commands({})["PythonVEnvInstall"] is nil. Running it gives E492: Not an editor command. The real commands are :Python venv install and :Python venv delete_select, which is what the README documents — it looks like these two strings were just missed in the move to the central :Python command (#21).
The first one is the one users actually meet, since it fires from the LspAttach autocmd on every *.py buffer in a project that isn't registered yet. Reaching for the name it prints is the natural next step, and it dead-ends.
Environment: macOS, nvim 0.12.5, commit 2e09bcb.
Suggested fix is just the two strings:
run :PythonVEnvInstall to create one -> run `:Python venv install` to create one
Use :PythonVEnvDeleteSelect to remove it. -> Use `:Python venv delete_select` to remove it.
Worth noting for the first message: I hit it on a uv project that already had a working .venv, so "venv not found ... create one" was doubly confusing — there was one, it just wasn't in state.json. That side of it is #37, and I've left the details there.
Two user-facing notifications still use the pre-
:Pythoncommand names, so they tell you to run something that isn't an editor command.lua/python/venv/detect.lua:208:lua/python/venv/create.lua:463:"python.nvim: Saved venv '%s' for cwd '%s'. Use :PythonVEnvDeleteSelect to remove it.",Neither is registered. In a Python buffer with the plugin loaded,
vim.api.nvim_get_commands({})returns onlyPythonandUV(plus unrelated ones from other plugins), andnvim_get_commands({})["PythonVEnvInstall"]is nil. Running it givesE492: Not an editor command. The real commands are:Python venv installand:Python venv delete_select, which is what the README documents — it looks like these two strings were just missed in the move to the central:Pythoncommand (#21).The first one is the one users actually meet, since it fires from the
LspAttachautocmd on every*.pybuffer in a project that isn't registered yet. Reaching for the name it prints is the natural next step, and it dead-ends.Environment: macOS, nvim 0.12.5, commit 2e09bcb.
Suggested fix is just the two strings:
Worth noting for the first message: I hit it on a uv project that already had a working
.venv, so "venv not found ... create one" was doubly confusing — there was one, it just wasn't instate.json. That side of it is #37, and I've left the details there.