For us, it was more the fact that we are locked down to a certain OS
version due to our local IT policy and the software repositories don't
provide a newer Python than v2.6.8. It was not the first occasion in terms
of desperately outdated software (recently it's gcc itself), so we are
used to compi
On Wed, Mar 23, 2016 at 10:54 PM, D K 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
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
On Tue, Mar 22, 2016 at 2:26 AM,
Same here for v2.7.11 on SLES 11. If you want to integrate as many modules
as possible at compilation time (we had to skip four unimportant ones in
the end) it may be painful with an older OS, but I assume CentOS is a bit
less recalcitrant than SLES.
We installed everything in home scheme, which re
We Iocally compile 2.7.8 and keep it in a distinct location that our paths
references.
This is very easy and has worked well for us.
Please excuse any typos -- Sent from my iPhone
> On Mar 21, 2016, at 5:32 PM, Peter Cock wrote:
>
> Hi D. K.,
>
> We're currently trying a locally compiled P
Hi D. K.,
We're currently trying a locally compiled Python 2.7 (from source)
under the shared Galaxy mount for use with a CentOS 6 cluster
and Galaxy server.
This seems to be working once we got the $PATH working for
cluster jobs (initially they would try to set the Galaxy metadata
using the syst
Hi Daniel,
I've been using python27 from CentOS Software Collections for quite some
time. It's a bit annoying because you have to remember to load it, but
it is surely doable.
Cheers,
Nicola
On 21/03/16 17:46, D K wrote:
Hi Galaxy Devs,
This may be premature but I read that for Galaxy after
Hi Galaxy Devs,
This may be premature but I read that for Galaxy after 16.01 that the plan
is for python 2.6 to no longer be supported. I'm currently running CentOS
6.6 which uses python 2.6. In order to be able to use newer versions of
Galaxy is my only option to upgrade to a newer version of Cen
