You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meza uses the system python - which is 3.6.8 currently on Rocky Linux 8. We should think about the overall effectiveness of using system python versus using a more flexible approach with venv.
The currently available Python is 3.12.x while 3.6.8 was released in 2018. RedHat backports security fixes even if the community does not support 3.6.x
In config/RedHat.yml where package_python3_pip: python36-pip is defined (differently than in Debian, and with an extra variable defined package_python3_pip_rhel8: python3-pip), is this actually necessary? I'm thinking that the correct version of pip3 would be constrained by the python that's installed. In any case, it's a variable, so figure out what you need for pip3 and install it. There shouldn't be two variables for pip3 depending on what OS release you have. There should be conditional logic about what pip3 gets installed depending on what OS release you have.
Meza uses the system python - which is 3.6.8 currently on Rocky Linux 8. We should think about the overall effectiveness of using system python versus using a more flexible approach with venv.
The currently available Python is 3.12.x while 3.6.8 was released in 2018. RedHat backports security fixes even if the community does not support 3.6.x
See discussion #8
The text was updated successfully, but these errors were encountered: