On 20/03/15 00:23, David Ripton wrote:
On 03/19/2015 08:05 AM, Phil Mayers wrote:
On 18/03/15 23:57, Glyph Lefkowitz wrote:
Rather than just suggest we preserve the status quo and stay on 2.6
forever to do indefinite free work to support Red Hat's obsolescence
You *definitely* shouldn't do that. Push back on RedHat, and tell
customers to push back on RedHat. I say this to other projects.
Red Hat supports old versions of RHEL forever because they have
customers that want that (because they have legacy apps that they want
to keep working with minimal maintenance, but who still want security
patches), and are willing to pay for it. It's a good thing that someone
provides that option, even if we don't all need it.
Absolutely, and we use it for that reason. But since RedHat charge for
this support, it seems fair they bear the maintenance burden ;o)
"Push back" could be "ask for an appropriate SCL" or some other way of
providing newer packages without violating the stability. The "samba"
versus "samba3x" packages on RHEL6 are a good example.
That doesn't mean Twisted needs to support old versions of RHEL forever.
RHEL 7 has been out for a while, and comes with Python 2.7 as the
default. So even if Twisted drops support for Python 2.6, it'll still
work on RHEL. (Just not on old versions of RHEL.)
Furthermore, SCL makes Python 2.7 available (in /opt) on RHEL 5 and 6
and CentOS 6, without users needing to build it themselves. So even
those who are stuck with old versions can install SCL, then use pip to
install new Twisted.
IOW, I wouldn't worry about it. Drop support for Python 2.6 when it
makes sense for Twisted.
+1
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
