Lines Matching full:python

48  - create a virtual environment in which all Python code runs during
125 Python virtual environments and the build process
128 An important step in ``configure`` is to create a Python virtual
129 environment (venv) during the configuration phase.  The Python interpreter
130 comes from the ``--python`` command line option, the ``$PYTHON`` variable
133 in how the build process runs Python code.
135 At this stage, ``configure`` also queries the chosen Python interpreter
140 PATH might operate in a different Python environment than the one chosen
150 virtual environment with ``pip``, either from wheels in ``python/wheels``
159               Currently, in all cases it would be possible to use ``python -m``
164               because the Python Packaging Authority provides a package
179 Bundled Python packages
182 Python packages that are **mandatory** dependencies to build QEMU,
188 ``python/scripts/vendor.py`` script.  The script embeds the
399 Meson has a special convention for invoking Python scripts: if their
401 find_program() arranges to invoke the script under the same Python
404 because it automatically uses the value of configure's --python= option.
406 In case the script is not written in Python, use a ``#! /usr/bin/env ...``
409 Scripts written in Python, where it is desirable to make the script
412 should be invoked through the ``python`` variable in meson.build. For
415   test('QAPI schema regression tests', python,
419 This is needed to obey the --python= option passed to the configure
423 By the time Meson runs, Python dependencies are available in the virtual
429        fs.parent(python.full_path()) / 'sphinx-build',
490 ``python/scripts/mkvenv.py``
491   A wrapper for the Python ``venv`` and ``distlib.scripts`` packages.
552   A Python virtual environment that is used for all Python code running