On Tue, 15 Apr 2025 12:10:26 -0600, Tom Rini wrote:
> 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.
>
> [...]
Applied to u-boot/master, thanks!
[1/1] python: Use and refer to the venv module rather than virtualenv
commit: efd00b03455644b18eaf2b6dcd07f6d55b95b39e
--
Tom
