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 slurm integration scripts in plugins/SLURM-Integration are launched via the ufm-{prolog,epilog}.sh scripts which launch them by running python3. However the python scripts themselves contain the shebang path /usr/bin/python, which depending on the system setup, can still point to the old python 2.x interpreter. Can you please fix so that python 2.x is not used by accident e.g. when testing?
I agree with the assessment of @jabl, can we fix this please? In addition, python files that are not meant to be executed directly should probably not be executable (like ufm_slurm_utils.py), nor have a shebang at all (ufm_slurm_base.py and ufm_slurm_utils.py).
The slurm integration scripts in
plugins/SLURM-Integration
are launched via theufm-{prolog,epilog}.sh
scripts which launch them by runningpython3
. However the python scripts themselves contain the shebang path/usr/bin/python
, which depending on the system setup, can still point to the old python 2.x interpreter. Can you please fix so that python 2.x is not used by accident e.g. when testing?The text was updated successfully, but these errors were encountered: