On Wed, Aug 11, 2010 at 11:29 PM, David Malcolm wrote:
> On Wed, 2010-08-11 at 14:48 +0200, Dennis Kaarsemaker wrote:
>> On Wed, Aug 11, 2010 at 2:20 AM, Russell Keith-Magee
>> wrote:
>>
>> > Like it or not, RHEL is still a major player in the enterprise market
>> > at the moment. I can't speak f
On Wed, 2010-08-11 at 14:48 +0200, Dennis Kaarsemaker wrote:
> On Wed, Aug 11, 2010 at 2:20 AM, Russell Keith-Magee
> wrote:
>
> > Like it or not, RHEL is still a major player in the enterprise market
> > at the moment. I can't speak for the US, but in Australia at least --
> > when all those com
Yeah - we're stuck with CentOS into the foreseeable future. Manually
compiling Python to a different prefix, and then recompiling mod_wsgi
and other modules against this version is really not an option at this
point. If Django 1.3 deprecated support for Python 2.4, then we would
be forced to remain
On Wed, Aug 11, 2010 at 2:20 AM, Russell Keith-Magee
wrote:
> Like it or not, RHEL is still a major player in the enterprise market
> at the moment. I can't speak for the US, but in Australia at least --
> when all those companies got on the Linux bandwagon in the mid 2000's,
> they all adopted R
On Tue, Aug 10, 2010 at 3:37 PM, Paul McMillan wrote:
> Django 1.2 dropped support for Python 2.3. In the past, there has been
> talk of dropping a version of Python per Django release. Python 2.4 is
> relatively rare these days, but still supported by RHEL.
>
> None of us like coding for it, and
Django 1.2 dropped support for Python 2.3. In the past, there has been
talk of dropping a version of Python per Django release. Python 2.4 is
relatively rare these days, but still supported by RHEL.
None of us like coding for it, and I know that several of the core
devs have voiced support in IRC
