Perhaps it is time...
I found a copy of Python 2.3 to load onto a new computer in order to test
my software, but it was not easy. It is in the small print about four
pages down from the download page on python.org. I was one of 432 people
who have downloaded the 2.3 installer for pywin32 build
[re supporting 2.3 for adodbapi]
Ditch it, I say. I think the minimum I test against for any of my stuff
is 2.4 -- and I'm more and more inclined towards 2.6+. As you say,
there's a small but definite overhead, the more so as we support 2.x and
3.x from the same codebase.
(I have to do some
Is it really worthwhile to keep maintaining support for Python 2.3, which
was released in 2005 and has not been updated since 2008?
my vote: keep the running versions, aka builds up to now downloadable.
Drop the support for more modern builds of PythonWin32. Whoever is
forced to work with
I've been happy to drop support for a couple of years, but while it kept
working I kept building it :) I can't recall if 2.4 is built with vc6
too - if so, we might as well kill that too.
Cheers,
Mark.
On 26/03/2013 8:33 PM, Vernon D. Cole wrote:
Perhaps it is time...
I found a copy of
+1
Mark Hammond skippy.hamm...@gmail.com wrote:
I've been happy to drop support for a couple of years, but while it
kept
working I kept building it :) I can't recall if 2.4 is built with vc6
too - if so, we might as well kill that too.
Cheers,
Mark.
On 26/03/2013 8:33 PM, Vernon D. Cole
Anyone running a no longer supported version of Python on Windows has
already made the conscious decision that upgrading their code to newer
versions is not worth the cost. No point in shifting that cost to pywin32
maintenance. +1 on dropping all code from any version of Python that no
longer
