Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A suggestion to use #!/usr/bin/env python instead of #!/usr/bin/python #3

Closed
mingzhi opened this issue Mar 16, 2016 · 4 comments
Closed

Comments

@mingzhi
Copy link
Contributor

mingzhi commented Mar 16, 2016

It is better to use #!/usr/bin/env python than #!/usr/bin/python, which can give user maximum flexibility to choose the interpreter to use. For example, in our HPC, there exists several versions of python and the default version (/usr/bin/python) is quite old. By loading other versions of python, we can not simply run run_phylo_cnv.py (after appending it to the PATH), but need to run "python scripts_dir/run_phylo_cnv.py".

@snayfach
Copy link
Owner

Good point - I'll think about doing this and updating the documentation (since users would need to use python run_phylo_cnv.py versus just run_phylo_cnv.py).

Also, did you run into an error when running run_phylo_cnv.py with the old version of python? If so, what is that version?

@snayfach
Copy link
Owner

Actually, never mind about needing to update the documentation. Users would still be able to use run_phylo_cnv.py

@mingzhi
Copy link
Contributor Author

mingzhi commented Mar 16, 2016

The default version of python in our HPC is 2.6.6. I never try to run PhyloCNV using this old version of python, since I need to install all the other packages, which I am not sure will be successful or not. And python 2.7 works fine.

@snayfach
Copy link
Owner

I've followed your recommendation and am now using #!/usr/bin/env python

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants