Python is easy to learn and use programming language; however, managing dependencies and package versions for it are nowhere as pleasant. One of the basic building block created to help with this is virtual environments. Join me in understanding how virtual environments work from within (by one of the project maintainers); also, to find out if the good old virtualenv project has any place left, now that Python 3.4+ contains venv. This talk is aimed to be a bit more technical in its first parts, presenting in technical details what a virtualenv is. The target audience is anyone who used virtual environments and wants to understand how they tick from within. I’ll also emphasise diversity and inclusion at Python interpreter level by highlighting other interpreters than CPython: Jython, PyPy or Iron Python. A concise outline goes as follows: What is a virtual environment? - why we need it - what we use it for - demo - virtualenv vs system env How do we build a virtual environment (CPython) - technical workflow of venv creation - activation -- bash -- powershell -- cmd.bat Other interpreters - why other than CPython? - PyPy - Jython - virtualenv - all Python support - extra activation - xonosh Summary and q/a