Thanks, I will try this tomorrow.
Fenglou
On 20 February 2014 22:32, Nate Coraor wrote:
> Hi Fenglou,
>
> In similar instances, I've simply compiled my own version of Python 2.7
> and placed it in a cluster-wide filesystem, then used the
> environment_setup_file option in universe_wsgi.ini to
Hi Fenglou,
In similar instances, I've simply compiled my own version of Python 2.7 and
placed it in a cluster-wide filesystem, then used the
environment_setup_file option in universe_wsgi.ini to ensure this version
is used when jobs run.
--nate
On Thu, Feb 20, 2014 at 3:31 PM, Fenglou Mao wro
Thanks for the answer. I am talking to our sysadmin to upgrade cluster nodes
from CentOS 5 to CentOS 6.
Fenglou
On Feb 20, 2014, at 2:18 PM, Dannon Baker wrote:
> Got it. We dropped the simplejson egg during the last release (and any you
> find are holdovers from previous versions of galaxy
Got it. We dropped the simplejson egg during the last release (and any you
find are holdovers from previous versions of galaxy) in favor of the stdlib
module. The relevant module from your find would have been
simplejson-2.1.1, and the rest are unrelated.
If possible, I'd *really* recommend upda
It is a little complicated here, The Galaxy server itself is running CentOS
6 with python 2.6, but the cluster nodes are running CentOS 5 with python
2.4. Mose jobs are running in the cluster nodes.
My questions is:
if there is a json module in galaxy-dist/eggs, why Galaxy is not picking it
up? If
The json module is included in python's standard library since python 2.6,
which is the minimum version of python Galaxy currently supports. Are you
using a python version older than that?
___
Please keep all replies on the list by using "rep
I just upgraded our galaxy server to the latest version, and I got this
error in many of the tools:
Traceback (most recent call last): File "./scripts/set_metadata.py", line
14, in ? import json ImportError: No module named json
And a "find" command below give many a few json eggs, please help. W
