Earlier today I tried running a JupyterLab converted executable python script in the terminal using ipython. However, my bash shell kept reading in an incorrect ipython path (that is probably tied to the first time I downloaded python). This meant that all of my regular python libraries could not be found…. I learned that I have several python paths probably due to various user inflicted python installations. Probably should clean that up at some point, but to not upset the python deities I did the next best thing (in my opinion).

To determine the directory of the ipython executable, type in the terminal:

ovesa:~$ which -a ipython
/usr/local/bin/ipython
/Users/ovesa/opt/anaconda3/bin/ipython

This shows all of the paths where this file was downloaded. The first path listed is the one that your bash shell goes to in order to find the command and launch it.

I wanted to use the ipython file associated with anaconda3, so I found this solution online:

ovesa:~$ python -m IPython

It apparently runs the ipython script stored in the directory associated with that python version which in my case is managed by the anaconda3 package.

To ensure that I do not completely self-destruct my precarious python arrangements, I added this into my bash script:

alias ipython = "python -m IPython"