I notice that cori.py does a module load for Python 3.5
# Remember to update this if you are using a different Python version
# on client side. Client and workers should have the same python env.
"overrides": """#SBATCH --constraint=haswell
module load python/3.5-anaconda ; source activate parsl_env_3.5"""
, but this repo uses f-strings (supported only from 3.6+). Does this not end up mattering because none of the actual bbpipe code runs on the compute nodes (which I think you call workers)? Why is there an insistence then that the client (login node?) and worker should have the same python version?
I notice that cori.py does a module load for Python 3.5
, but this repo uses f-strings (supported only from 3.6+). Does this not end up mattering because none of the actual bbpipe code runs on the compute nodes (which I think you call workers)? Why is there an insistence then that the client (login node?) and worker should have the same python version?