On Thu, Oct 22, 2009 at 5:51 PM, "Martin v. Löwis" <span dir="ltr"><<a href="mailto:martin@v.loewis.de" target="_blank">martin@v.loewis.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>> From the Django roadmap for supporting 3.0, using 2.6 as a stepping<br>
> stone (and if 2.7 was a *better* stepping stone then it would make it<br>
> easier):<br>
><br>
> <a href="http://groups.google.com/group/django-developers/msg/0888b1c8f2518059" target="_blank">http://groups.google.com/group/django-developers/msg/0888b1c8f2518059</a>?<br>
<br>
</div>Is that still a current plan? It's from November 2008.<br>
<div><br></div></blockquote><div><br>Django 1.1 came out in 2H09, not 1H09, and Django 1.2 is now looking to come out in 1H10, not 2H09, so the dates in that note have slipped out by 3-6 months. (The labeling of some features as must-have for a release has been dropped for 1.2, so as to hopefully prevent the kind of slip seen with 1.1.) Django 1.2 is still scheduled to drop Python 2.3 support. I think it's too early to say whether Python 2.4 support will be dropped with 1.3, nor do I have any good idea when supporting 3.x will become a priority.<br>
<br>Karen<br><br><br></div></div>