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 metadata: ......
twisted 12.3.0 py27_0 defaults
12.3.0 py26_0 defaults
13.0.0 py27_0 defaults
13.0.0 py26_0 defaults
13.1.0 py27_0 defaults
13.1.0 py26_0 defaults
13.2.0 py27_0 defaults
13.2.0 py26_0 defaults
14.0.0 py27_0 defaults
14.0.0 py26_0 defaults
14.0.2 py27_0 defaults
14.0.2 py26_0 defaults
15.0.0 py27_0 defaults
15.0.0 py26_0 defaults
15.1.0 py27_0 defaults
15.1.0 py26_0 defaults
15.2.0 py34_0 defaults
15.2.0 py27_0 defaults
15.2.0 py26_0 defaults
15.2.1 py34_0 defaults
. 15.2.1 py27_0 defaults
15.2.1 py26_0 defaults
15.3.0 py34_0 defaults
15.3.0 py27_0 defaults
15.3.0 py26_0 defaults
15.4.0 py35_0 defaults
15.4.0 py34_0 defaults
15.4.0 py27_0 defaults
15.5.0 py35_0 defaults
15.5.0 py34_0 defaults
* 15.5.0 py27_0 defaults
Steve
On 12/15/2015 11:40 AM, 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.
Just takes a few minutes to get everything installed and running.
On Tue, Dec 15, 2015 at 6:30 AM, Phil Mayers <[email protected]
<mailto:[email protected]>> wrote:
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
packages, so
it won't break anything. Since you're a CentOS 6.7 user, the
standard
SCL should work (it's 6.5+).
I really disliked the SCLs when I looked at it. The supported
use-case seems to be a kind of hugely over-engineered set of
wrapper/environment setup scripts:
scl enable python2.7 pip install blah
...ad infinitum.
Personally - and I guess for others as well - the SCLs will be
off-putting. It's a shame there isn't a simpler solution, namely
EPEL python2.7 - having a 2nd python in a different path is quite
safe, we do it routinely.
It's hugely annoying that RHEL6 and derivatives missed out on Python
2.7 :o(
_______________________________________________
Twisted-Python mailing list
[email protected]
<mailto:[email protected]>
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
--
Raymond Cote, President
voice: +1.603.924.6079 email: [email protected] skype:
ray.cote
_______________________________________________
Twisted-Python mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________
Twisted-Python mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
