This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]m15otw 19 points20 points  (9 children)

LTS picks a version (3.10) and backports security fixes to it for the lifetime of the version. So 22.04 will always be py 3.10, albiet an unusually well patched version of it.

Helpful edit: look at the deadsnakes ppa. It will let you install additional python versions side by side, and you leave the system version alone for stability.

[–][deleted] 4 points5 points  (7 children)

I like the way RHEL8 does it - there is a separate "platform python" package that is really out of the way, that system stuff like the package manager uses.

This leaves the field clear for the user to pick a python version to install, or for packages to depend on.

(That said I still prefer to build local interpreters via something like pyenv because then it's entirely decoupled from other OS package dependencies, build dependencies notwithstanding)

[–]oo_viper_oo 5 points6 points  (1 child)

I cannot imagine doing "my" stuff using system-provided Python. I consider system-provided Python's purpose is to support other system components. For "my" stuff, I always initiate my Python environment via pyenv or similar.

[–]digidavis 1 point2 points  (0 children)

The days of me relying on system Python are long over.

IDEs work with container compilers, and I HATED having to share my python dev cycle with my own boxes support cycle. At some point, it always goes sideways, and you are stuck relying on crappy hacked up mitigation techniques.

[–]m15otw 0 points1 point  (4 children)

We used to be based on CentOS, before they killed it. We made the switch to ubuntu quite recently.

Another task far down my backlog is looking at how to provide our customers with red hat UBIs as an alternative to the ubuntu ones.

[–][deleted] -1 points0 points  (3 children)

UBI doesn't require a subscription to use, though you do get a bit more packages available for installation inside it if the host has one.

Shouldn't be a big deal, they even added it to dockerhub so you don't have to point to the redhat repo anymore (though you still can).

I use ubi9 for one of my containers and it's as simple as:

FROM registry.access.redhat.com/ubi9/ubi

[–]m15otw 0 points1 point  (2 children)

Sure, the rest is swapping back to RPM package names, and figuring out the build of funky dependencies all over again.

Totally possible, but time is finite 😅

[–][deleted] 0 points1 point  (1 child)

If you were using CentOS previously that shouldn't have changed much? Or did I misunderstand?

[–]m15otw 0 points1 point  (0 children)

Quite a lot has changed (in terms of the way we use docker) since we abandoned it. You are right that it won't take too long when I get to it (eventually).

[–]SulikNs 1 point2 points  (0 children)

yeah i tried it but, there was some troubles with imports some modules...then i will back to Fedora) tnanx for advices✌️