Re: Last patch breaks Py 2.3 compatibility

Chris Lambacher <[email protected]> Fri, 8 Jul 2011 11:00:49 -0400
Newsgroups gmane.comp.python.formencode
Message-ID <CAAXXHgKJzpTqRJa3e5rsZ8T6diw6sZ3-gp8XwwLh7o3dX0XOGw@mail.gmail.com>
On Thu, Jul 7, 2011 at 6:05 AM, Christoph Zwerschke <[email protected]> wrote:
> Am 07.07.2011 00:04 schrieb Ian Bicking:
>> I ended up reverting that change because it also broke tests, and once I
>> looked at it I didn't understand the purpose anyway.  Not that I mind
>> dropping 2.3 support ;)
>
> Since the 2to3 patch by Graham Higgins also requires Py 2.4, dropping
> 2.3 support would be a step forward I think.
+1

2.3 is getting pretty long in the tooth and 2.4 is a fairly large
milestone release.

>
> If we drop it, I am willing to go through the code and simplify it based
> on Py 2.4 (use decorators etc.)

You have something specific in mind here?

> But I suggest creating a final 1.2.5 release with Py 2.3 support before
> doing this and then having a 1.3 which requires Py 2.4 after the
> overhaul, maybe already with Graham's patch.

+1

We should also triage any critical bugs before a 1.2.5 release and
make sure that we don't have to maintain 1.2.x for a long time. Any
idea about the user base still on 2.3?


-Chris Lambacher

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2