On Fri, 2023-08-25 at 13:03 +0000, Jeremy Stanley wrote:
On 2023-08-25 10:16:29 +0200 (+0200), Thomas Goirand wrote: [...]
I kind of like the idea in this thread to have a venv where we would run the latest RC version of the interpreter. This would be lighter than maintaining another image, no? At least this way, this gives upstream OpenStack the opportunity to be closer to distros, where as currently, the project is lagging 1 year and 1 interpreter version behind...
The ensure-python role used by most of OpenStack's test jobs supports installing Python in other ways than from distro packages already, that just happens to be its default method. If you set the python_use_pyenv[*] flag then it will clone and install pyenv[**] from GitHub and proceed to build the requested Python interpreter/stdlib version.
The main downsides I see for not using a prebuilt Python packages is that the effected jobs are going to end up building Python from source on every run, and there's still no guarantee that we have an available platform where the requested Python version can be built successfully.
i was kind of wondering if we could optimise the proces by using dib to bake in the ones we want into the image but it kind of comes down to a question of how often this would run. i.e. if it a weekly periodic building in the job is probaly ok if it per patch probably not.
[*] https://zuul-ci.org/docs/zuul-jobs/latest/python-roles.html#rolevar-ensure-p... [**] https://github.com/pyenv/pyenv