Tom Rini efd00b0345 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 <trini@konsulko.com>		2025-04-24 15:37:27 -06:00
..
buildman.rst	buildman: Convert documentation to rST	2022-11-22 15:13:34 -07:00
clang.rst	doc: clang: Update and correct support notes	2023-12-05 01:38:56 +01:00
docker.rst	doc: build: docker: Use code-block for syntax highlighting	2025-04-03 09:04:35 +02:00
documentation.rst	doc: Update documentation URL	2023-12-13 18:39:05 -05:00
gcc.rst	python: Use and refer to the venv module rather than virtualenv	2025-04-24 15:37:27 -06:00
gen_compile_commands.rst	doc: build: fix gen_compile_commands section level	2024-04-13 11:03:12 +02:00
index.rst	doc: add documentation for gen_compile_commands.py	2023-10-11 13:24:55 -04:00
reproducible.rst	buildman: Add a flag for reproducible builds	2023-03-08 11:38:48 -08:00
source.rst	doc: shorten overlong title underlines	2023-11-11 01:44:08 +01:00
tools.rst	Allow Python packages to be dropped	2023-09-22 06:03:46 +08:00