3 ms·
Pro-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
by kstrauser 7y ago
Pro-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 7y 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.