Re: [galaxy-user] Install problems on OS X with python from macports

Hi Nate, Your fix works for the scramble fine, but not for the run.sh which now fails. On removing the -ES from run.sh, I get an error importing simplejson (see below). simplejson.egg is in the eggs/py2.5-noplatform dir so I dont' see why it doesn't pick this up if it manages to pick up WebHelpers. Traceback (most recent call last): File "./scripts/paster.py", line 26, in <module> command.run() File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteScript-1.3.6-py2.5.egg/paste/script/command.py", line 78, in run File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteScript-1.3.6-py2.5.egg/paste/script/command.py", line 117, in invoke File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteScript-1.3.6-py2.5.egg/paste/script/command.py", line 212, in run File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteScript-1.3.6-py2.5.egg/paste/script/serve.py", line 227, in command File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteScript-1.3.6-py2.5.egg/paste/script/serve.py", line 250, in loadapp File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 193, in loadapp File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 213, in loadobj File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 237, in loadcontext File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 267, in _loadconfig File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 397, in get_context File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 439, in _context_from_explicit File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/PasteDeploy-1.3.1-py2.5.egg/paste/deploy/loadwsgi.py", line 18, in import_string File "/Users/james/Src/galaxy_dist/lib/pkg_resources.py", line 1912, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/Users/james/Src/galaxy_dist/lib/galaxy/web/__init__.py", line 5, in <module> from framework import expose, json, require_login, url_for, error, form, FormBuilder File "/Users/james/Src/galaxy_dist/lib/galaxy/web/framework/__init__.py", line 17, in <module> import webhelpers File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/WebHelpers-0.2-py2.5.egg/webhelpers/__init__.py", line 1, in <module> File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/WebHelpers-0.2-py2.5.egg/webhelpers/rails/__init__.py", line 7, in <module> File "/Users/james/Src/galaxy_dist/eggs/py2.5-noplatform/WebHelpers-0.2-py2.5.egg/webhelpers/rails/scriptaculous.py", line 16, in <module> ImportError: No module named simplejson 2008/9/12 Nate Coraor <nate@bx.psu.edu>:

The problem is this: _hashlib.so and zlib.so live in site-packages because macports bundles them separately. Since you do python -S these cannot be seen. The quick fix was to copy these files from site-packages into the python dir, which I will probably forget about when I upgrade ;) This raises the question of why you are being so protective over your python path? Presumbaly this was discussed before. thanks, James 2008/9/15 James Casbon <casbon@gmail.com>:

Hi James, Is this to say that it resolved your problem in the message below (importing simplejson)? The reason for -ES: site or PYTHONPATH installed dependencies often conflict with those dependencies provided with Galaxy. Since setuptools doesn't currently offer a method to continue trying the search path when adding dependencies, conflicting versions in the path almost always cause problems. For example, if you had Cheetah 2.x in your PYTHONPATH or site-installed and it happened to be found before ours, loading would fail, since setuptools would see the wrong version and never continue down the path to find the correct version. --nate James Casbon wrote:

2008/9/15 Nate Coraor <nate@bx.psu.edu>:
Yes. I think this is a MacPorts issue. If python -S doesn't get you python, it's their problem, right?
The joys of setuptools! Thanks for taking the time to help. Now I have it up and running I hope to integrate some tools. I love the work you have done with the workflow interface. cheers, James
participants (2)
-
James Casbon
-
Nate Coraor