I don’t really know why calling the interpreter with the full path wouldn’t work for you. I use it all the time. But if you want to use the Python interpreter that is in your environment, you should do: #!/usr/bin/env python That way you search your environment for the Python interpreter to use.
[July 2021] If you see this message when running eval “$(pyenv init -)” WARNING: `pyenv init -` no longer sets PATH. Run `pyenv init` to see the necessary changes to make to your configuration. you should check the message from pyenv init as the warning says, but in a nutshell, you can use eval “$(pyenv … Read more
Pyenv and virtualenv are very different tools that work in different ways to do different things: Pyenv is a bash extension – will not work on Windows – that intercepts your calls to python, pip, etc., to direct them to one of several of the system python tool-chains. So you always have all the libraries … Read more
Edit: It’s worth mentioning pip here as well, as conda and pip have similarities and differences that are relevant to this topic. pip: the Python Package Manager. You might think of pip as the python equivalent of the ruby gem command pip is not included with python by default. You may install Python using homebrew, … Read more
This is my personal recommendation for beginners: start by learning virtualenv and pip, tools which work with both Python 2 and 3 and in a variety of situations, and pick up other tools once you start needing them. Now on to the answer to the question: what is the difference between these simalarly named things: … Read more