Background I’ve been using the excellent lazy.nvim package manager for more than three years now, and I’ve been super happy with it. But with Neovim v0.12.0, vim.pack was shipped: a built-in (but still experimental) plugin manager that manages plugins using Git, with no third-party dependencies required, implemented by Evgeni Chasnovski (see neovim/neovim#34009), known for his work on mini.nvim. This piqued my interest, as I’ve found myself creating abstractions and isolations with lazy.nvim that don’t harmonize with my grug brain. So I figured I wanted to see if I could simplify by moving onto vim.pack.

[@rob](https://gts.cupcakerob.nl/@rob)

If you use poetry to manage your venv for each repo, you can also do: poetry shell to use start the virtualenv, and then run nvim . to start coding.

Provided that your dap is setup like this:

local dap = require("dap")  
dap.configurations.python = {  
 {  
 type = "python",  
 request = "launch",  
 name = "Launch file",  
 program = "${file}",  
 pythonPath = "python",  
 },  
}  

[#nvim](https://mastodon.world/tags/nvim) [#neovim](https://mastodon.world/tags/neovim) [#python](https://mastodon.world/tags/python)