CheckM2
CheckM2 copied to clipboard
[Feature Request] Use #!/usr/bin/env python instead of hardcoding python path
I have a pretty unique installation. I have conda environments that I've built on an EC2 that are stored on EFS. I have a separate EC2 for submitting SLURM jobs so the absolute path of the conda environment will be a little different. I noticed that the main checkm2 executable has the python interpreter hardcoded.
Would it be possible to use #!/usr/bin/env python instead so it grabs whatever Python is in the environment instead of the hardcoded path when building the package?