Best practice on using virtual environments in Python

[bytecrunch]

Thank you. But after you create a virtual environment and also activated it,

VS Code, PyCharm will detect the environment or just choice from a list of Interpreter.
Example.

# Make 
G:\div_code
λ python -m venv my_env
# cd in
λ cd my_env\
# Activate
λ G:\div_code\my_env\Scripts\activate
# Start VS Code
G:\div_code\my_env
(my_env) λ code .

As i start VS Code from environment,it will usually auto detect the environment,see 3.12('my_env': venv).
This work the the same for Anaconda/Miniconda as you have ask about before,
also poetry(stable mature now) is good choice if making a package(share on eg PyPi).

Great! Thank you. All clear now: enter the activated environment and launch the IDE, like VS code....I am sure we can go the other way: launch VS code and activate the virtual environment from the VS Code terminal...which is also a terminal...

What is different between the VS Code terminal and the regular Windows terminal like CMD or Powershell?

Jupyter notebook, another IDE, has these things call kernels that makes things less clear. Jupyter is a client-server application that runs on a single machine locally. What is the kernel about in this case?