rmtew added the comment:
False alarm, must have reproduced this in wrong source tree :-( Purely
Stackless-specific.
--
resolution: -> invalid
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
New submission from rmtew :
Platform Windows 7.
hg id: a3f2dba93743+ (3.2)
I do not know any reproduction steps for this bug outside as a side-effect
within an incomplete and problematic Stackless merge. This bug also seems to
exist in cpython, and is not in Stackless specific code.
It
rmtew added the comment:
Attached is a patch to fix the issue, generated using "p4 diff -du" which
should hopefully be usable.
--
keywords: +patch
Added file: http://bugs.python.org/file23044/zlibmodule.patch
___
Python trac
New submission from rmtew :
zlibmodule.c calling inflateInit2 and deflateInit2 will subsequently proceed to
crash in the case where these functions return Z_VERSION_ERROR.
zlib implementation note:
When you compile against zlib, several functions (actually macros) like
inflateInit2 and
New submission from rmtew :
File: Lib\test\test_socket.py
Code:
class UDPTimeoutTest(SocketTCPTest):
Problem:
This test is intended to test UDP sockets, but derives from SocketTCPTest.
Logic dictates this should derive from SocketUDPTest.
I've searched for UDP (with differing cas
New submission from rmtew :
OS: Windows 7
Compiler: Visual Studio 2008
Build: Win32 (Debug and Release)
The main problem is observed in both debug and release builds, and even though
the test effectively passes in both it also fails in release build.
** In a debug build I see the following
