Re: [galaxy-dev] ImportError: No module named json

2014-02-20 Thread Dannon Baker
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

Re: [galaxy-dev] ImportError: No module named json

2014-02-20 Thread Fenglou Mao
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?

Re: [galaxy-dev] ImportError: No module named json

2014-02-20 Thread Dannon Baker
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

Re: [galaxy-dev] ImportError: No module named json

2014-02-20 Thread Fenglou Mao
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 dannon.ba...@gmail.com wrote: Got it. We dropped the simplejson egg during the last release (and any you find are holdovers from

Re: [galaxy-dev] ImportError: No module named json

2014-02-20 Thread Fenglou Mao
Thanks, I will try this tomorrow. Fenglou On 20 February 2014 22:32, Nate Coraor n...@bx.psu.edu 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