Python path is unexpected, have you sourced ../conf/offload.env?
This is because we have a check verifying that the Python we are using is the one inside the installation directory.
In the new GOE we do not bundle a Python interpreter with the software therefore I think the check is redundant.
In issue https://github.com/gluent/goe/issues/31 we are evaluating how to package Python dependencies which might result in an executable of some kind but I still think this check is redundant.
Unless you can think of a good reason not to then remove the check on sys.exec_prefix from each executable.
When running executables we see this message:
This is because we have a check verifying that the Python we are using is the one inside the installation directory.
In the new GOE we do not bundle a Python interpreter with the software therefore I think the check is redundant.
In issue https://github.com/gluent/goe/issues/31 we are evaluating how to package Python dependencies which might result in an executable of some kind but I still think this check is redundant.
Unless you can think of a good reason not to then remove the check on
sys.exec_prefixfrom each executable.