3 ms·
I made the transition from PyCharm to VSCode a couple of days ago and... it's not been smooth. Virtualenv doesn't automatically activate when I first open the w
by petargyurov 6y ago
I made the transition from PyCharm to VSCode a couple of days ago and... it's not been smooth. Virtualenv doesn't automatically activate when I first open the workspace, pylint doesn't work yet VSCode thinks it's working and debugging just doesn't seem to work full stop.
I need to get back to it and try to fix it because I do like VSCode as a whole.
- zomglings 6y agoOne thing that helps me managing Python environments in VS Code: I start VSCode from the command line with my virtual environment activated ("code -n ."). With this, I rarely have issues with VSCode picking up my environment. Hope that is of some use to you.
- petargyurov 6y agoI will try it, thanks.
- kstrauser 6y agoPro-tip for VSCode: if you have a .venv directory in the root of your project, VSCode will try to activate it when you open the project. A few other tools have adopted that convention, too, and now at my job so have we. Rather than sticking virtualenvs in some odd location, the venv for ~/projects/mystuff is ~/projects/mystuff/.venv, and now it almost always Just Works.
- petargyurov 6y agoMine is in the root directory but it's called venv, without the preceeding dot. I'll dig around the settings to see if I can change what it looks for. Strangely it works if I close the initial termnial it spawns and open a new one.