Build RV using a Python virtual environment

[chxmberland]

Linked issues

N/A

Summarize your change.

The Python version included with MacOS Sonoma 14.5 adopted PEP 668, which is meant to prevent conflicts between system level Python packages with project specific Python packages, like what is included in requirements.txt.

This means that the user will encounter an error when attempting to install Python requirements unless they use the tag --break-system-packages tag. By using a virtual environment, system-level conflicts are avoided and the user has a safer build of Open RV.

Describe what you have tested and on which operating system.

Mac OS Sonoma 14.5 and Windows 11.

If possible, provide screenshots.

PEP 668 error without a virtual environment, triggered by running rvbuild.

[chxmberland]

Please don't name it pyenv. Pyenv is a different thing and might confuse people (I got confused at first).

venv (or .venv) is is fine.

Also, can you run rvenv multiple times without errors?

Just made the change! Also, it looks like you can run rvenv as many times as you'd like without any issue, and complete the build normally afterwards.

[eloisebrosseau]

Would you mind adding your changes to the README so that it reflects the contents of rvcmds.sh?

[linux-foundation-easycla[bot]]

• :white_check_mark: login: chxmberland / name: Ben Chamberland (cd12d404be3ddf02126eaf99e3155a7066d8449d, 7747e363e9704e91edc06ffaee0f8fa130d4afac)
• :x: The email address for the commit (39576ddb521c548b7712018d8e5f49d82dbc71dc) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[chxmberland]

Horribly mangled git history. This PR has been moved here: https://github.com/AcademySoftwareFoundation/OpenRV/pull/536