I concur. I am one of the 100 downloads of 2.5 -- and the only reason I
download it is to test it, not to use it in production. How many of the
other downloaders are like me? Most, I would bet. Dropping 2.5 would allow
use of many Python3 features, since 2.6 has the backports for them (print
function, "{}".format(), byte literals, and especially "except ... as"). It
would simplify the Python code in the library.
On Wed, Apr 15, 2015 at 4:25 AM, Tim Golden <m...@timgolden.me.uk> wrote:
> On 15/04/2015 10:11, Mark Hammond wrote:
> > Hi Tim,
> > I still build for 2.5 and 3.1, but really only because they do still
> > build. If there's a reasonable reason to drop support for some I doubt
> > it will hurt many people - the sourceforge page should show you download
> > stats, but last I looked 2.5 was rarely used then, and that was some
> > time ago!
>
>
> FWIW the sf page for build 219 shows less than 100 downloads for 2.5/6
> and 3.1/2.
>
> Unsuprisingly 2.7 dominates with 3,000 downloads at 32-bit (2,000 at
> 64-bit).
>
> 3.3 comes in just over 100 and 3.4/5 each a few hundreds.
>
> So I feel no particular compunction about dropping forward support for
> 2.6 and lower and 3.2 and lower. (Could say 2.5/3.1 but it's the same
> SDK level I think).
>
> TJG
> _______________________________________________
> python-win32 mailing list
> python-win32@python.org
> https://mail.python.org/mailman/listinfo/python-win32
>
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
