We Keep Coding

I activate venv in vscode but it doesnt appear in terminal

I have no idea whats going on but I activated venv by using Scripts/activate and it doesnt working yet, the (venv) isnt appearing
please someone could help me? I tried everything I could find lol

It looks like you are using Git Bash or a similar bash-like system for Windows. You need to run Scripts/activate.sh in this environment.
For PowerShell, use Scripts/activate.ps1, and for cmd use Scripts/activate.bat.

What terminal are you using? Please create a new powershell or cmd terminal. Also you should not open the folder of the virtual environment as a workspace. Below are the correct steps.
Create a new folder as a workspace, then open this folder in vscode
Create a new terminal using the following command to create a virtual environment
python -m venv .venv
Use the following command to activate the environment after creation
.venv\scripts\activate
Another way is to select the interpreter of the virtual environment in the Select Interpreter panel after creating the environment
And then the new terminal will automatically activate the environment
You can read creating-environments and venv.

Why doesn't my project's virtual env auto-launch in VS Code?

VS Code v1.58.1
Python v3.92
In a python project, I set up a virtual environment. In this project folder, I have a sub-folder .vscode that contains a file settings.json, which has the following contents (pointer to the project's virtual environment folder):
{
"python.defaultInterpreterPath": "D:\\Documents\\coding\\pyproj1\\proj_env\\Scripts\\python.exe",
"python.terminal.activateEnvironment": true
}
When I open this project folder in VS Code, the powershell terminal does not automatically launch the virtual environment, and in the lower left corner of VS Code, the virtual environment python interpreter is not listed. When I run a new terminal in VS Code, the virtual env is still not activated.
I had the same problem when I was using python.pythonPath which I understand is now deprecated in favor of python.defaultInterpreterPath.
If I leave VS Code alone for a few minutes after opening the project folder, it will sometimes select the virtual env interpreter. But since I'm telling VS Code where it is, why isn't it selecting this at folder open?
Where am I going wrong?

The python.defaultInterpreterPath setting only works at the first time.
After you manually select the python interpreter, the VSCode will remember it. When you reopen the VSCode, it will select the interpreter the last time you have selected. And the python.defaultInterpreterPath setting will have no influence anymore.
But you take this command to reset it: Python:Clear Workspace Interpreter Setting.
Update:
You can set the python.defaultInterpreterPath like this:
"python.defaultInterpreterPath": ".venv\\Scripts\\python.exe"
It looks like has some problem with your Python extension or the cache.
Could you try to:
Reinstall the python extension. Remember to delete the extension folder under: C:\Users\${UserName}\.vscode\extensions
Delete all the files under these locations:
C:\Users\${UserName}\AppData\Roaming\Code\User\globalStorage
C:\Users\${UserName}\AppData\Roaming\Code\User\workspaceStorage
Or you can empty the folder of:
C:\Users\${UserName}\AppData\Roaming\Code
But remember to storage the settings.json under
C:\Users\${UserName}\AppData\Roaming\Code\User

As described in the earlier comment: "So it seems my issue is that VS Code does not remember the interpreter I used last time."
What resolved the issue is deleting the virtual env and recreating it. Now when I open the project folder, VS Code auto activates the virtual env.
Steps involved for anyone wishing to do the same:
activate virtual env
create requirements file: pip freeze > requirements.txt
deactivate to exit venv
rm proj_env or whatever the name of the venv folder is
create virtual env, e.g., python -m venv proj_env
activate the virtual env (VS Code may detect the venv during creation, and ask if you wish to activate venv, go ahead and say Yes)
pip install -r requirements.txt to install the requirements into the virtual env

VSCode does not recognize venv

When I create a new project and the virtual environment using the venv python package, VSCode doesn't recognize the new virtual environment. I follow the bellow instruction:
https://code.visualstudio.com/docs/python/environments
The command that I use in the VSCode integrated terminal is:
python -m venv .venv
The terminal that I use is PowerShell 7, But I tried the CMD terminal too.
After running this command, the .venv folder is created very well on the workspace and I checked its behavior on the terminal.
I tried conda package manager to create a venv and VSCode recognizes it. The problem is only with the venv Python package.
I also tried another Python version to create venv, But the problem still exists.
I read this question:
How can I set up a virtual environment for Python in Visual Studio Code?
I know how to add an environment manually, but I expect VSCode to recognize my environments automatically.
I added these lines to settings.json (Preferences):
"python.venvPath": "~/.venv",
"python.venvFolders": [
"~/.venv/Scripts"
]
I activated the venv manually using VSCode integrated terminal.
The problem still isn't solved.
This is a screenshot of my problem:
I know how to add an environment manually, but I want it to be automatic.
I tried VSCode on another PC, and it worked; It doesn't need anything to do except the presence of venv.
VSCode Version: 1.58.0
Python Extension Version: v2021.6.944021595

The "python.venvPath" should be set to the parent folder of the .venv folder.
Virtual environments located in the folder identified by the
python.venvPath setting (see General settings), which can contain
multiple virtual environments. The extension looks for virtual
environments in the first-level subfolders of venvPath.
But, you need not set that. The Python extension should find the venv environment, as it is just located under your workspace folder.
Virtual environments located directly under the workspace (project)
folder.
I tried it locally, it does not work too. It will only show the cached environment path, and the "python.venvPath" does not work either.
And there are some changes of the interpreter storage:
A VSCode internal storage is introduced which will now store the
interpreter settings in the workspace & workspace folder scope.
You can refer to here for more details.
So, it's recommended to select the environment path manually for now.

After writing this command in VS CodeTerminal
python -m venv env
You can simply use
.\env\Scripts\Activate
In the same directory path where you have created the virtual enviroment.

For some reason VSCode had uninstalled all my Python extensions including the main Python extension. After reinstalling them it was able to detect my virtualenvs again.

So I was having this same issue and I resolved it by,
1. Open Settings in VSCode.
2. Search for "python.terminal.activateEnvironment"
3. If unchecked/unticked, then check/tick for both "User" and "Workspace".
The problem is not with VSCode but the workspace settings in which I was working on.
Just changed that and Voila works like a charm.

How to autoload venv/bin/activate in vscode on mac

I have django project folder with venv environment.
when opening vscode it has terminal opened in vscode.
Is there a way that I don't have to venv/bin/activate all the time when opening the project folder?

Edit (credit to #XJOJIX) from the comment in this answer. This will active the virtual environment without having to close or open terminals. A Python file still needs to be selected to load the Python extension.
Add this parameter in VS Code to "launch.json" or ".code-workspace"
"settings": {
"python.terminal.activateEnvInCurrentTerminal": true
}
Previous Answer:
To have a VS Code terminal automatically activate a virtual environment when first launching VS Code:
Close the terminal before exiting VS Code.
Open VS Code. Ensure a Python file is selected to direct VS Code to load the Python extension.
Wait for the Python extension to finishing loading (very bottom
left of VS Code terminal).
Open a new terminal after Python extension has loaded. The venv will automatically activate.
The trick is to open the terminal only after the Python extension has loaded.
If the directory of the terminal contains a virtual environment, VS Code will also automatically activate a virtual environment if a new terminal is opened. As before, a Python file must be selected and the Python extension must be fully loaded.

If you are on a mac OS, the simplest thing is to make ENV for your python projects.
Follow these simple Command in your Vs Code Terminal and you get your ENV activated :
Python3 -m venv env
source env/bin/activate
(The env in the first line is your env name so you can type any name)

Use the command palette to trigger the "Python: select interpreter" command. It should allow you to pick your virtual environment.
The article Using Python environments in VS Code migth be of interest to you.

If you use window machine, it might locate at
env/Scripts/activate
You can run above in your vscode terminal to activate your venv

How to set a Python Interpreter from inside a existing virtual environment in Visual Studio code

I want to open an existing virtual environment in Visual Studio Code. When I try to change the interpreter address inside of the settings.json (as instructed by https://code.visualstudio.com/docs/python/environments#_global-virtual-and-conda-environments) it doesn't work. With the virtual environment that I have, there is no python.exe file, I believe that is the issue as to why the following settings.json file doesn't work.
{
"python.pythonPath": "D:\\GitProjects\\OrganizationApp\\venv1\\bin\\python"
}

First of all Try open the root folder which venv folder resides in with Visual Studio Code.
(If you are on Linux you can just got the directory and open terminal and type code).
You should get a pop up to change the interpreter.
If not then Open your command palette Ctrl + Shift + P
Search for Python interpreter and select the Venv one.

According to your description, you could refer to the following steps to check the creation and use of the virtual environment in VSCode:
Prerequisites.
Check if python is available.
Enter cmd from the computer, enter the cmd window, enter python, and output the python version number to represent python is available.
If it is not available, please check the python installation package and check the python environment variables.
The python extension was successfully installed in VSCode.
Create and use a virtual environment:
Create a virtual environment in the vscode terminal. python3 -m venv ./venv1 or python -m venv ./venv1 Reference: virtual environments.
Select Yes when the prompt box pops up.
Then the interpreter will automatically be replaced with the created virtual environment.
After restarting VSCode, there is no python interpreter displayed in the lower left corner. We can create or open a python file and it will automatically display the interpreter.
Click on the interpreter to choose other available interpreters.
Use the shortcut key Ctrl+Shift+` to open a new terminal and enter the virtual environment.
Update:
When I open other projects or don’t open any project in VSCode , the virtual environment created before is not displayed in the python interpreter options. The reason is that the virtual environment we created is based on the current project and it exists in this project. like this:
Although this virtual environment is not displayed in other projects, I can use this virtual environment by selecting the python.exe of the virtual environment ( 'enter interpreter path' '.venv' 'Scripts'). Therefore, if there is no python.exe, it is recommended to create a new virtual environment.