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.

Sign up for GitHub

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

Jump to bottom

Question re: /usr/bin/env python #2

Open
gklimowicz opened this issue Aug 25, 2024 · 1 comment · May be fixed by #4
Open

Question re: /usr/bin/env python #2

gklimowicz opened this issue Aug 25, 2024 · 1 comment · May be fixed by #4
Labels
question Further information is requested

Comments

@gklimowicz
Copy link
Collaborator

I'm a Python avoider, on macOS. I have python3 installed via homebrew. Running

./run_tests.py -c gfortran -C gcc

gives

env: python: No such file or directory

Brew doesn't seem to install a python, just a python3.

What's the canonical way that Python programmers specify which python to resolve to?

/usr/bin/env python3?

Or coerce the homebrew install to make me a link from python to python3?

Or create it manually? (Ick.)
@gklimowicz gklimowicz added the question Further information is requested label Aug 25, 2024
@everythingfunctional
Copy link
Member

Good question. I don't use Python for much these days either, so I'm not really sure if there's a "canonical" way. /usr/bin/env python3 seems reasonable to me, but I also expect a lot of Python users are doing python3 ./run_tests.py -c gfortran -C gcc.

@MarDiehl MarDiehl linked a pull request Nov 17, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

more common executable name MarDiehl/fortran-compiler-test-suite
2 participants
@gklimowicz @everythingfunctional