On Wed, Nov 26, 2008 at 1:30 AM, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Tuesday 25 November 2008 01:02:03 Rob Hudson wrote:
>> Hi Django Devs,
>>
>> I saw that ticket[1] made it into the 1.1 list and I was drawn to
>> it. I have a project that will be doing some mass sending of emails
>>
On Nov 27, 2:13 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> * Solaris: I'm unable to find information detailing which Python
> version ships with various releases of Solaris and OpenSolaris. If
> anyone has that information, please post it in a reply.
Solaris versions prior to 10 did
On Thu, Nov 27, 2008 at 7:20 AM, Tim Chase
<[EMAIL PROTECTED]> wrote:
> So I'm somewhere between -0 and -1 on the voting scale regarding
> forced/long-range Python-version deprecation. But when a version
> becomes sufficiently dead weight, slowing down Django's progress
> like 2.3 seems to be
On Nov 27, 2008, at 8:20 AM, Tim Chase wrote:
>
> However, I haven't seen any/much expression of *want* that 2.4 be
> dropped any time in the near future (and there are a much larger
> number of 2.4 deployments). I wouldn't schedule that "2.4 will
> be dropped in Django 1.3" timetable, but
James Bennett wrote:
> Apologies for the length of this email,
Thanks, James, for your post-doctoral dissertation on the History
and Cumulative Predicted Future of Python Versions and Their
Interrelations With the Django Development Process. :-) (joking
aside, it was an appreciated and
Le 27 nov. 08 à 02:39, Eduardo O. Padoan a écrit :
>
> On Tue, Nov 25, 2008 at 3:08 PM, Jacob Kaplan-Moss
> <[EMAIL PROTECTED]> wrote:
>>
>> Hi folks --
>>
>> I'd like to officially drop Python 2.3 support in Django 1.1.
>> Discuss.
>>
>> Jacob
>
> +1 -- because reusable apps developers could
