Vanilla Local Galaxy Installation Is Giving Error: "No Module Called Eggs"

Question

[JacobS]

Hi, sorry for the installation-related question, but I was hoping someone might know a quick fix. While installing Galaxy on my local machine (with Python 2.7.3), I am getting the following error upon commanding sh run.sh:

Initializing tool-data/srma_index.loc from srma_index.loc.sample
Initializing tool-data/twobit.loc from twobit.loc.sample
Initializing static/welcome.html from welcome.html.sample
Traceback (most recent call last):
  File "./scripts/check_eggs.py", line 32, in <module>
    from galaxy.eggs import Crate
ImportError: No module named eggs
Some eggs are out of date, attempting to fetch...
Traceback (most recent call last):
  File "./scripts/fetch_eggs.py", line 28, in <module>
    from galaxy.eggs import Crate, EggNotFetchable
ImportError: No module named eggs
Fetch failed.

Has anyone encountered this before?

[David Quigley]

You'll need to install the chicken module; unfortunately, that one has a dependency on eggs, so it's hard to know what to suggest.

[Istvan Albert]

well done, for a second there I mused on the potential complexities of circular imports

Answer 1

[Nate Coraor]

The check_eggs.py and fetch_eggs.py scripts automatically add Galaxy's lib/ directory to Python's sys.path, albeit at the end. It looks like you may have something on your sys.path named galaxy that is being found before galaxy-dist/lib/galaxy/. What does the output of python -c 'import galaxy; print galaxy' show?

Answer 2

[Istvan Albert]

that pretty much looks like an import error one would get if files were missing or the path was incorrect.

look into the galaxy package and it whould have an eggs module.

another possibility is that you are running this in a manner where the run.sh cannot properly set the import path

Answer 3

[indexofire]

make sure galaxy is in python sys.path