On Wed, Mar 23, 2016 at 10:54 PM, D K <danielforti...@gmail.com> wrote:
> Great! thanks for the suggestions. I just tried using centos software
> collections and that seems to work. I'll do some more testing but hopefully
> it's as simple as that! Is there any reason that most of you who responded
> have decided to compile your own pythons?
>
> D

It sounds like both options are effective.

In my case it was perhaps a choice out of ignorance about just how the
CentOS software collections works - and fear about the CentOS 6 to 7
migration.

In our case both the Galaxy server and the cluster is still on CentOS 6,
so we need to use a custom Python 2.7 on both the Galaxy server and
also on the cluster nodes - ideally the exact same version so that all
the wheel dependencies match up for running the set metadata scripts.

I'm hoping that using a custom Python 2.7 installation (from source)
ought to work in our favour if we have to deal with a mixture of CentOS
6 and 7 (although ideally we'd update the cluster and Galaxy server
together).

Regards,

Peter
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to