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/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
Thanks Amber!
In which case, I'll take steps to workaround #4811 until next year.
I should add, I'm very grateful and excited that we got so many releases
out this year. It's a wonderful thing to see.
On Mon, 14 Dec 2015 at 15:13 Amber "Hawkie" Brown
wrote:
> Hi!
>
> Since a release went out j
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
"pisymbol ." writes:
> The fact is the Python community at large then needs to convince the
> distro maintainers accordingly. Telling a customer to update their
> entire platform for a newer version of Python isn't going to fly a lot
> of times (and remember, someone of them have support agreemen
