The only back-pressure you might get would be from RHEL4, which is still python 2.3. However, it is nearing its end of life and only promises security updates. In my mind, I wouldn't worry too much about it.<br><br><div class="gmail_quote">
On Fri, Jul 31, 2009 at 9:59 AM, P.J. Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm thinking about dropping support for Python 2.3 shortly. Mainly, I'd like to start requiring Python 2.4 in the 0.7 series of setuptools, as this will allow me to drop some kludgery.<br>
<br>
In general, however, I'd also like to start dropping Python 2.3 support from other packages, with an emphasis on phasing out the quirkier aspects of DecoratorTools usage. Also, 2.4 has built-in sets, threading.local, datetime, unittest-doctest support, etc. etc. -- all of which (and more) there are numerous backport kludges for in PEAK projects.<br>
<br>
Any thoughts?<br>
<br>
_______________________________________________<br>
PEAK mailing list<br>
<a href="mailto:PEAK@eby-sarna.com" target="_blank">PEAK@eby-sarna.com</a><br>
<a href="http://www.eby-sarna.com/mailman/listinfo/peak" target="_blank">http://www.eby-sarna.com/mailman/listinfo/peak</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="mailto:kylev@kylev.com">kylev@kylev.com</a><br> Some people have a way with words, while others... erm... thingy.<br><br>