Lines Matching full:environment
24 A virtual environment is created on top of an existing
25 Python installation, known as the virtual environment's "base" Python, and may
26 optionally be isolated from the packages in the base environment,
27 so only those explicitly installed in the virtual environment are available.
29 When used from within a virtual environment, common installation tools such as
30 `pip`_ will install Python packages into a virtual environment
38 …python.org/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment>`__
52 When a Python interpreter is running from a virtual environment,
54 point to the directories of the virtual environment,
56 point to those of the base Python used to create the environment.
59 running from a virtual environment.
61 A virtual environment may be "activated" using a script in its binary directory
64 :program:`python` will invoke the environment's Python interpreter
68 containing the virtual environment):
71 | Platform | Shell | Command to activate virtual environment |
93 You don't specifically *need* to activate a virtual environment,
94 as you can just specify the full path to that environment's
96 Furthermore, all scripts installed in the environment
100 a "shebang" line which points to the environment's Python interpreter,
106 without the environment needing to be activated or on the :envvar:`!PATH`.
108 When a virtual environment has been activated, the :envvar:`!VIRTUAL_ENV`
109 environment variable is set to the path of the environment.
110 Since explicitly activating a virtual environment is not required to use it,
112 whether a virtual environment is being used.
115 environment to be activated, their shebang lines contain the absolute paths
116 to their environment's interpreters. Because of this, environments are
118 simple means of recreating an environment (for example, if you have a
120 requirements.txt`` using the environment's ``pip`` to install all of the
121 packages needed by the environment). If for any reason you need to move the
122 environment to a new location, you should recreate it at the desired
123 location and delete the one at the old location. If you move an environment
125 environment in its new location. Otherwise, software installed into the
126 environment may not work as expected.
128 You can deactivate a virtual environment by typing ``deactivate`` in your shell.
141 mechanisms for third-party virtual environment creators to customize environment
152 site-packages should be available to the environment (defaults to ``False``).
155 any existing target directory, before creating the environment.
161 environment with the running Python - for use when that Python has been
165 installed in the virtual environment. This uses :mod:`ensurepip` with
168 * ``prompt`` -- a String to be used after virtual environment is activated
169 (defaults to ``None`` which means directory name of the environment would
184 Creators of third-party virtual environment tools will be free to use the
191 Create a virtual environment by specifying the target directory
193 virtual environment. The ``create`` method will either create the
194 environment in the specified directory, or raise an appropriate
202 Create a virtualized Python environment in a directory.
203 env_dir is the target directory to create an environment in.
218 Creates the environment directory and all necessary subdirectories that
222 ``clear=True``, contents of the environment directory will be cleared
228 * ``env_dir`` - The location of the virtual environment. Used for
231 * ``env_name`` - The name of the virtual environment. Used for
238 environment. This takes into account the case where a virtual environment
239 is created from another virtual environment.
241 * ``inc_path`` - The include path for the virtual environment.
243 * ``lib_path`` - The purelib path for the virtual environment.
245 * ``bin_path`` - The script path for the virtual environment.
248 environment location. Used for ``__VENV_BIN_NAME__`` in activation
252 environment. Used for ``__VENV_PYTHON__`` in activation scripts
257 the virtual environment.
271 Creates the ``pyvenv.cfg`` configuration file in the environment.
275 Creates a copy or symlink to the Python executable in the environment.
283 environment.
288 ``setuptools``) in the environment. This is done by shelling out to the
289 ``pip`` executable in the environment.
296 implementations to pre-install packages in the virtual environment or
311 assist in installing custom scripts into the virtual environment.
317 directory in the environment. The contents of "common" and the
321 * ``__VENV_DIR__`` is replaced with the absolute path of the environment
324 * ``__VENV_NAME__`` is replaced with the environment name (final path
325 segment of environment directory).
327 * ``__VENV_PROMPT__`` is replaced with the prompt (the environment
334 environment's executable.
336 The directories are allowed to exist (for when an existing environment
363 subclass which installs setuptools and pip into a created virtual environment::
377 easy_install other packages into the created virtual environment.
380 created virtual environment.
382 virtual environment.
408 virtual environment being created.
410 :param context: The information for the virtual environment
445 # Download script into the virtual environment's binaries folder
457 # Install in the virtual environment
476 Install setuptools in the virtual environment.
478 :param context: The information for the virtual environment
492 Install pip in the virtual environment.
494 :param context: The information for the virtual environment
519 'virtual environment.')
523 "virtual environment.")
527 "environment.")
530 help='Give the virtual environment access to the '
543 'virtual environment '
546 'environment creation.')
549 'environment directory to '