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
The ansible runner 2.10 and 2.11 images using python 3.8, which is not the platform python for EL8. ansible/ansible-runner#595
ansible-runner uses pip to install, while we have made an effort to build dependencies like python-kubernetes and python-openshift as RPMs, albeit originally for the sake of other projects where we required packages.
Unfortunately these packages build against the platform python and won't work with the version of python ansible-runner is using.
Three options I can think of
Build modules for python 3.8
Wait for an EL9 base image
Use pip to install our dependencies
I'm not fond of the idea of building a python 3.8 module package. It's likely to require lots of work on dependencies that aren't packaged for 3.8, even beyond what I/we are already maintaining for the platform python.
Even if we get an EL9 package that fixes the situation we're likely to end up back here eventually.
In reality using pip is probably not likely to cause too many problems, despite my preference for properly packaged dependencies.
The text was updated successfully, but these errors were encountered:
The ansible runner 2.10 and 2.11 images using python 3.8, which is not the platform python for EL8.
ansible/ansible-runner#595
ansible-runner uses pip to install, while we have made an effort to build dependencies like python-kubernetes and python-openshift as RPMs, albeit originally for the sake of other projects where we required packages.
Unfortunately these packages build against the platform python and won't work with the version of python ansible-runner is using.
Three options I can think of
I'm not fond of the idea of building a python 3.8 module package. It's likely to require lots of work on dependencies that aren't packaged for 3.8, even beyond what I/we are already maintaining for the platform python.
Even if we get an EL9 package that fixes the situation we're likely to end up back here eventually.
In reality using pip is probably not likely to cause too many problems, despite my preference for properly packaged dependencies.
The text was updated successfully, but these errors were encountered: