Peter wrote:
You started Galaxy using Python 2.5, but when Galaxy starts a child process for the python tool it would default to the system python I think, which must still be Python 2.4.
One solution I'd try would be to hack the tool's XML file to change <command interpreter="python"> to be explicit, <command interpreter="python2.5">
Although I see that Brad fixed this, it's probably worth pointing out that you wouldn't normally need to go to this much trouble. Rather than having to edit all the tools, you can simply ensure that the first `python` on your $PATH is the version you need. Instructions for this can be found as "Step 0" on http://getgalaxy.org . You can also use a Python virtualenv, the process for which is explained in the production server documentation at: http://usegalaxy.org/production --nate
The better fix would be in scripts/nglims/add_ng_defaults.py to make it Python 2.4 compatible. I think this just means replacing lines 51 and 52,
with open(config["nglims_config_file"]) as in_handle: nglims_config = yaml.load(in_handle)
with:
in_handle = open(config["nglims_config_file"]) nglims_config = yaml.load(in_handle) in_handle.close()
Right Brad? ;)
Then try again, and hope that is the only thing blocking this from working on Python 2.4. I didn't see any more with statements so fingers crossed.
Peter
P.S. Current version is here: http://bitbucket.org/chapmanb/galaxy-central/src/tip/scripts/nglims/add_ng_d...
_______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev