0

After a fresh install of anaconda and a fresh install of Rodeo, I'm still getting:

There was an error running python when I try to set my path.

When I type which python into terminal, I get: /Library/anaconda/bin/python

Looking at my ~/.bash_profile, I have the following:

export PATH="/opt/local/bin:/opt/local/sbin:$PATH"
export PATH="/Library/anaconda/bin:$PATH"
export PATH="/Library/cling_jupyter/bin:$PATH"

When I try to set my which python path in Rodeo:

enter image description here

I get:

enter image description here

The weird thing is... the last output from the error:

enter image description here

Is an old path from an old anaconda installation.

And the other weird thing:

enter image description here

I have two 'pythons' in my bin folder. One is a .app and the other is an alias that actually points to the python3.5 file.

I have tried the following:

But nothing has worked. Please help! I'd really love to get Rodeo on my system.

emehex
  • 9,874
  • 10
  • 54
  • 100

1 Answers1

1

It looks like you have multiple anaconda's on your machine and the /Library one isn't configured correctly, so Rodeo is reverting to an old one.

Easiest thing to fix this is to remove anaconda completely and reinstall. I'd check out this post on uninstalling.

The "normal" spot for anaconda to install is your home directory: ~/

Other things to check:

  • Running which -a python will list all the pythons on your system.
  • Running which -a conda will list all the condas on your system.
  • Check your .bashrc and .bash_profiles to make sure there aren't any rogue python paths being exported

(also be sure you have jupyter installed as well: pip install jupyter)

Community
  • 1
  • 1
  • Running `which -a conda` just lists one anaconda, however, `which -a python` shows two pythons: (1) /Library/anaconda/bin/python (2) /usr/bin/python. (2) seems to be the offending python? `.bashrc` doesn't exist on my machine. But the paths in `.bash_profiles` seem to be okay. Any thoughts? – emehex Dec 02 '16 at 18:33
  • 1
    I ended up nuking my computer and starting from a fresh install. Rodeo is now up and running... never could figure out the root cause (I have a feeling it had something to do with a Cling Kernel for Jupyter installation gone wrong) – emehex Dec 14 '16 at 19:51