How do you all handle this? I’m going to start poking around with NixOS but anticipate Python dev to be impossible on the base OS, so curious what sorts of options y’all use when connecting your configured editor to a container- e.g. if I have Neovim configured in my host, is it better to re-set-up Neovim again with the same dotfiles in the container and dev in the container, or connect the editor to the container somehow?
My gut is saying it’s probably cleaner to set up an editor inside the container, just not sure I want to do that every time I start a project.
deleted by creator
Python is easy on NixOS, you just need to use python venvs and you can use pip like normal
(python -m venv .venv) to create the venv (only need to do once per project)
.venv/bin/activate to enable the venv (Vscode should do this automatically if you create the venv through the python extension)
Then just pip install to your heart’s content
(Probably a good idea to pip freeze > requirements.txt every time you install a new library too to make it reproducible
Also you should probably add the venv directory to gitignore if you’re using git as it’ll add a lot of crap to source control that can be easily regenerated from the requirements.txt
In my experience, you still have your same path to your nix installed binaries in the distribox container, so you shouldnt even have to duplicate your configuration. I also dont suspect python dev to be that bad so long as you use venv or conda.
Neovim is not a CLI editor, it is a TUI editor. If you want a CLI editor, use
edorex.
