Setting up a Python virtual environment in 2023

Python uses its "virtual environment" mechanism to let you isolate a project's requirements from other Python projects in your system. Learn in this video how to set up a virtual environment with your project, manage it with pip to add the requirements you need, and what quirks and behaviors you need to know to work with a venv effectively using modern Python.
-----------------------------­---
SUBSCRIBE: kzbin.info_c...
FACEBOOK: / infoworld
TWITTER: / infoworld
WEBSITE: www.infoworld.com/

[@uiiisa]

Very clear and useful explanation, thanks.

[@cherryxd6849]

damn such a good video ty

[@HiltonFernandes]

I supposed that you were going to comment newer alternatives to venv, like poetry and virtualenv.

[@Jubijub]

+1, that would have been a more useful video, in particular in combination with pyenv, but also in its own right.

[@InfoWorld]

That's an excellent idea, and one worth laying out in a future video. Stay tuned! -Serdar

[@CanDoSo_org]

Thanks. But I am always confused with modules. Sometimes I've already installed a module, but it says "Module does not found!" How to install a module which can be used by all environment?

[@InfoWorld]

When you install a module, it's meant to be installed in one environment at a time, to prevent conflicts. This is why pyproject.toml (and before it, requirements.txt) let you automate setting up an environment for a project so you don't have to do that over and over again. Make sure you're installing your requirements to the correct environment, and not to the underlying Python installation either. -Serdar

[@CanDoSo_org]

Thanks, Serdar.@@InfoWorld

[@moritzmller5761]

That's why I hate Python. Does not replicate. On a default Python (3.11) installation on Linux (latest Ubuntu) there is no `py` alias. That's where a beginner would get lost. So if you run `python3 -m venv .env` you get the `.env` folder but you neither get `main.py` nor do you get a `.env/Scripts` folder. Instead you get an `.env/bin` folder. With different `[a|A]ctivate.*` scripts for different shells. You need to know which one to source. Not run! E.g. if you're on zsh or bash the command is `source .env/bin/activate`. But if you're on c-shell it is `source .env/bin/activate.csh` etc. Every time I have to use Python I wonder if it is the P in PITA. :)