+1 here.
Python versions shipped by systems still matter, imo.
Some python bindings, like python-libvirt, python-ceph, python-selinux are not provided by pip, so they must be built against python version needed manually, which is really not always a straightforward process.
Despite pyenv looks very appealing at first glance, it brings quite some challenges for deployments at the end.
And even if distro does provide higher version of python itself during lifetime, they do never provide all required bindings to it, which makes it very tough to use (or well, same as with pyenv basically).
On 2/13/24 16:04, Mohammed Naser wrote:
> Hi Niklas,
>
> These are all awesome ideas, I support them and I think we should take
> that initiative.
>
> Also, I think the Python versions don't matter as much these days, I
> feel that almost most deploying tools are exploring some form of
> containerization so co-installability and all that aren't that much of
> an issue.
I strongly do not agree with the above sentence. Co-installability is
still a thing, it's not because *you* are using containers that everyone
loves it. We're also moving toward using Kube for some part of the
control plane, but we'll be continuing to use packages in the pods, and
support bare-metal setup in the distro.
Cheers,
Thomas Goirand (zigo)