[Martin v. L?wis wrote]
Raymond Hettinger wrote:
I'd guess this belongs in 2.5, with a possible retrofit for 2.4.
+1 on backporting, but that is up to Anthony.
Correct me if I'm wrong - but there isn't much porting to this.
AFAICT, this is only relevant for the Windows build (i.e.
[Scott David Daniels]
I'd guess this belongs in 2.5, with a possible retrofit for 2.4.
[Raymond Hettinger]
+1 on backporting, but that is up to Anthony.
[Martin v. L?wis wrote]
Correct me if I'm wrong - but there isn't much porting to this.
AFAICT, this is only relevant for the Windows build
[Trent Mick]
Here is a patch to do this (attached) that works on the trunk and
against the Python-2.4.1.tgz source tarball. Shall I check this into the
HEAD and release24-maint?
[Tim Peters wrote]
Definitely on HEAD, almost certainly on 24 maint. The slight
uncertainty wrt the latter is
[Anthony Baxter wrote]
On Tuesday 26 July 2005 11:39, Trent Mick wrote:
Here is a patch to do this (attached) that works on the trunk and
against the Python-2.4.1.tgz source tarball. Shall I check this into the
HEAD and release24-maint?
Yes.
Okay, done.
Can I say that I've had the
Raymond Hettinger wrote:
I'd guess this belongs in 2.5, with a possible retrofit for 2.4.
+1 on backporting, but that is up to Anthony.
Correct me if I'm wrong - but there isn't much porting to this.
AFAICT, this is only relevant for the Windows build (i.e. which
version is used in the
Note zlib 1.2.3 is just out -- the zlib compression/decompression
http://www.zlib.net/
From the page:
Version 1.2.3 eliminates potential security vulnerabilities in zlib
1.2.1 and 1.2.2, so all users of those versions should upgrade
immediately. The following important fixes
Note zlib 1.2.3 is just out -- the zlib compression/decompression
. . .
I'd guess this belongs in 2.5, with a possible retrofit for 2.4.
+1 on backporting, but that is up to Anthony.
Raymond
___
Python-Dev mailing list
Python-Dev@python.org
