On Wed, Nov 26, 2008 at 7:23 AM, varikin <[EMAIL PROTECTED]> wrote: > On Nov 25, 7:16 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: >> However, even saying Django 1.1 is the last 2.3-compatible version and >> we drop it afterwards gives us a reasonable 3.0 support timeline, since >> our timeframe doesn't really encourage any official 3.0 support for 1.1. > > I am +1 to saying 1.1 is the last release for 2.3 (or just deprecated > and dropped sometime in the future). Pulling support for something is > large step and was never discussed for 1.1 openly till now. Anyone who > has read the roadmap but not following any more than that could be in > for a nasty surprise.
Actually, dropping 2.3 support was openly discussed for 1.0 at PyCon 2008. In a room with at least 60 developers, I was the only one that raised my hand when Jacob asked about people using Python 2.3 (I had RHEL4 boxes in production). Also at PyCon, the core developers later decided to keep 2.3 support for 1.0 and drop it shortly afterwards (Jacob, looks like we still need to post those meeting minutes: http://www.djangoproject.com/foundation/records/). Digging through my notes here, it seems that a big reason for keeping Python 2.3 support for 1.0 was for the benefit of the Jython/IronPython/PyPy folks. I'm not sure how these areas have come along since then. jython.org seems down at the moment, but from the IronPython page, I gather they are at CPython 2.4 and 2.5 compatibility levels [1] with their 1.x and 2.x releases, respectively. If Python 2.3 support still helps these folks then then I would be in favor of keeping 2.3 support around for 1.1. Otherwise, I'm all for dropping 2.3 support, as maintaining 2.3 support is not fun at all. Just dig through changesets and note all of the 2.3 bugs that were introduced and fixed over the last major development cycle, for example. Python 2.3 unicode bugs have been the most annoying, but there have been a few rsplit, list generator, and other syntax bugs as well. Testing is made easier, too, since it means one less version of Python to test against. As for the roadmap, I think that is the point of this discussion. We are finalizing the features for 1.1, and if Python 2.3 support is to be dropped, then this fact will indeed need to be noted on the roadmap along with the other planned features. Those needing to stay on Python 2.3 could just keep to 1.0.x, not unreasonable if you ask me. Also, 1.1 is still four months away and 1.0.x will be receiving bug fixes until then, so Python 2.3 users wouldn't be completely left in the dark. Gary [1] http://www.codeplex.com/IronPython/Wiki/View.aspx?title=Differences --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
