Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by matsemann on Tuesday April 05, 2022 @10:01AM
(#30919072)
Have you tried VSCode's remote abilities? Should do exactly as you describe. https://code.visualstudio.com/docs/remote/remote-overview or https://devblogs.microsoft.com/python/remote-python-developm...
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by antholeole on Tuesday April 05, 2022 @10:58AM
(#30919861)
I’ve seen these and got it to work this way. I’m not too fond of working inside the container as it’s just a little more friction, but I’ve been working this way for a little bit now. I was hoping to avoid working in the container.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by nevalsar on Tuesday April 05, 2022 @09:57AM
(#30919027)
Try this:
1. Bring up command palette using `Ctrl+Shift+p`
2. Search and select "Python: Select Interpreter"
3. Select your Python environment.
This works in VSCode over SSH perfectly fine - the locally running VSCode is able to detect and select Python environments in the remote server.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by antholeole on Tuesday April 05, 2022 @10:56AM
(#30919837)
The trouble with this is that the python environment is in the container - In step 2, id need to type path to the interpreter that it inside the container.
Although, now you’ve got me thinking what would happen if I mounted the interpreter inside the container to something local that I can point to? Might try this later, thanks for the help!
I did some googling, but I’m unfortunately not experienced enough to be able to describe the problem succinctly to google.
Using pylance, btw.
TIA!