Lines Matching full:venv

36 <https://docs.python.org/3/library/venv.html>`_ (venvs) that expose a specific
39 When a Pigweed GN build starts a single venv is created for use by all
43 the venv. Of course if a new third-party package dependency is added it will be
50    **Every pw_python_action is run inside a venv**
64         subgraph pyactions1[Python venv 1]
66           venv1(fa:fa-folder out/python-venv &nbsp)
73         subgraph pyactions2[Python venv 2]
75           venv2(fa:fa-folder out/another-venv &nbsp)
84    Pigweed uses `this venv target
86    if a project does not specify it's own build venv. See
87    :bdg-ref-primary-line:`docs-python-build-python-gn-venv` on how to define
88    your own default venv.
90 Having a static venv containing only third-party dependencies opens the flood
91 gates for python scripts to run. If the venv only contains third-party
115 .. _docs-python-build-python-gn-venv:
120 <https://docs.python.org/3/library/venv.html>`_ for executing Python code. This
125 There must be at least one venv for Python defined in GN. There can be multiple
128 The default build venv is specified via a GN arg and is best set in the root
138    optional ``venv`` argument to specify which Python venv it should run
147 the bootstrapped environment and in the GN build venv. There are two main ways
196 A given venv inherits a project's requirements and constraint files by default
205 GN targets expected to be used within the venv. When the venv is created each
223    :start-after: [downstream-project-venv]
224    :end-before: [downstream-project-venv]
641        # The default venv for Python actions in GN
643        # use this venv.
648          path = "$root_build_dir/python-venv"
652          # Ensure all third party Python dependencies are installed into this venv.
672        # Python venv.