diff options
| author | Tom Rini <[email protected]> | 2025-04-15 12:10:26 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-04-24 15:37:27 -0600 |
| commit | efd00b03455644b18eaf2b6dcd07f6d55b95b39e (patch) | |
| tree | 037d898da2753ccf92134099cc643e51b7b3d38d /doc/build | |
| parent | 10f48365112b164bee6564033ab682747efcb483 (diff) | |
python: Use and refer to the venv module rather than virtualenv
Using some form of sandbox with Python modules is a long standing best
practice with the language. There are a number of ways to have a Python
sandbox be created. At this point in time, it seems the Python community
is moving towards using the "venv" module provided with Python rather
than a separate tool. To match that we make the following changes:
- Refer to a "Python sandbox" rather than virtualenv in comments, etc.
- Install the python3-venv module in our container and not virtualenv.
- In our CI files, invoke "python -m venv" rather than "virtualenv".
- In documentation, tell users to install python3-venv and not
virtualenv.
Signed-off-by: Tom Rini <[email protected]>
Diffstat (limited to 'doc/build')
| -rw-r--r-- | doc/build/gcc.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/gcc.rst b/doc/build/gcc.rst index d8fcfdc4bf2..480e0e3091e 100644 --- a/doc/build/gcc.rst +++ b/doc/build/gcc.rst @@ -31,7 +31,7 @@ Depending on the build targets further packages maybe needed python3-pkg-resources python3-pycryptodome python3-pyelftools \ python3-pytest python3-pytest-xdist python3-sphinxcontrib.apidoc \ python3-sphinx-rtd-theme python3-subunit python3-testtools \ - python3-virtualenv swig uuid-dev + python3-venv swig uuid-dev SUSE based ~~~~~~~~~~ |