On 15/12/2015 16:40, Ray Cote wrote:
We have a fair bit of Python 2.7 Twisted code deployed on RHEL and
CentOS 5 and 6.
In each case, we build from source and do a make altinstall so we’re
running a Python separate from the system’s.
We build an RPM, but basically yes; put it in a different pat
Here (NASA/GSFC) we use conda-based virtual envs on CentOS 6, and
they work great -- I turned our sysadmins on to conda about a year
ago, and they *love* it (no more compiling python, woo! ;)
All recent versions of twisted are available as conda packages:
# conda search twisted
Fetching package me
We have a fair bit of Python 2.7 Twisted code deployed on RHEL and CentOS 5
and 6.
In each case, we build from source and do a make altinstall so we’re
running a Python separate from the system’s.
Just takes a few minutes to get everything installed and running.
On Tue, Dec 15, 2015 at 6:30 AM, Ph
On 15/12/15 04:16, Amber "Hawkie" Brown wrote:
There is a solution to this, and Nick Coghlan has mentioned it to me
many times -- Software Collections for RHEL and CentOS. Software
Collections is RH's answer to "new software" on "stable
distributions" -- SCLs operate side-by-side with system pa
Sorry if the quoting is a little weird in this, I've long since deleted
Glyph's original response, so I'm replying to Amber's latest, but I just
noticed something in the quote (from Glyph, I think) that I want to correct
for the sake of posterity:
> On 15 Dec 2015, at 08:43, Glyph Lefkowitz wro
> On 15 Dec 2015, at 08:43, Glyph Lefkowitz wrote:
>
>>> But again: Python 2.6 is unsupported by the upstream Python developers. You
>>> really should not be using it, since it won't receive security updates (of
>>> course, Red Hat and transitively CentOS claim to "support" these packages,
>>>
