<br><br><div class="gmail_quote">On Wed, Dec 21, 2011 at 2:57 AM, Jim Fulton <span dir="ltr"><<a href="mailto:jim@zope.com">jim@zope.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Dec 21, 2011 at 2:15 AM, Chris Withers <<a href="mailto:chris@simplistix.co.uk">chris@simplistix.co.uk</a>> wrote:<br>
> Hi All,<br>
><br>
> What's the general consensus on supporting Python 2.5 nowadays?<br>
><br>
> Do people still have to use this in commercial environments or is everyone<br>
> on 2.6+ nowadays?<br>
><br>
> I'm finally getting some continuous integration set up for my packages and<br>
> it's highlighting some 2.5 compatibility issues. I'm wondering whether to<br>
> fix those (lots of ugly "from __future__ import with_statement" everywhere)<br>
> or just to drop Python 2.5 support.<br>
><br>
> What do people feel?<br>
<br>
</div>Google app engine is still Python 2.5, as is Jython.<br></blockquote><div><br></div><div>There's work being done to change that on the app engine front: <a href="http://code.google.com/appengine/docs/python/python27/newin27.html">http://code.google.com/appengine/docs/python/python27/newin27.html</a></div>
<div><br></div><div>-gps</div></div>