..code-block::console

``virtualenvmy_project`` will create a folder in the current directory which will

``virtualenvvenv`` will create a folder in the current directory which will

contain the Python executable files, and a copy of the ``pip`` library which you

can use to install other packages. The name of the virtual environment (in this

case, it was ``my_project``) can be anything; omitting the name will place the files

case, it was ``venv``) can be anything; omitting the name will place the files

in the current directory instead.

..note::

'venv' is the general convention used globally. As it is readily available in ignore files (eg: .gitignore')

This creates a copy of Python in whichever directory you ran the command in,

placing it in a folder named:file:`my_project`.

placing it in a folder named:file:`venv`.

You can also use the Python interpreter of your choice (like

``python2.7``).

..code-block::console

or change the interpreter globally with an env variable in ``~/.bashrc``:

..code-block::console

The name of the current virtual environment will now appear on the left of

the prompt (e.g. ``(my_project)Your-Computer:your_project UserName$)`` to let you know

the prompt (e.g. ``(venv)Your-Computer:your_project UserName$)`` to let you know

that it's active. From now on, any package that you install using pip will be

placed in the ``my_project`` folder, isolated from the global Python installation.

placed in the ``venv`` folder, isolated from the global Python installation.

For Windows, same command which is mentioned in step 1 can be used for creation of virtual environment. But, to activate, we use the following command.

Assuming that you are in project directory:

..code-block::powershell

Install packages as usual, for example:

littered across your system, and it's possible you'll forget their names or

where they were placed.

..note::

Python has included venv module from version 3.3. For more details: `venv<https://docs.python.org/3/library/venv.html>`_.

Other Notes