[issue8650] zlibmodule.c isn't 64-bit clean

2011-05-14 Thread Nadeem Vawda
Nadeem Vawda added the comment: Fixed in 3.1, 3.2 and 3.3. 2.7 no longer has this problem -- the fix for issue8651 ensures that the functions cannot receive inputs large enough to be problematic (since we don't define PY_SSIZE_T_CLEAN). -- resolution: -> fixed stage: needs patch -> co

[issue8650] zlibmodule.c isn't 64-bit clean

2011-05-14 Thread Roundup Robot
Roundup Robot added the comment: New changeset 0b5211d19a14 by Nadeem Vawda in branch '3.1': Issue #8650: Make zlib.[de]compressobj().[de]compress() 64-bit clean. http://hg.python.org/cpython/rev/0b5211d19a14 New changeset 3ff862d05d18 by Nadeem Vawda in branch '3.2': Merge: #8650: Make zlib.[d

[issue8650] zlibmodule.c isn't 64-bit clean

2011-05-14 Thread Roundup Robot
Roundup Robot added the comment: New changeset 850624632e9a by Nadeem Vawda in branch '3.1': Issue #8650: Backport 64-bit safety fixes for compress() and decompress(). http://hg.python.org/cpython/rev/850624632e9a New changeset 99a3ce22c1ff by Nadeem Vawda in branch '3.2': Null merge (#8650): z

[issue8650] zlibmodule.c isn't 64-bit clean

2011-03-20 Thread STINNER Victor
STINNER Victor added the comment: > This only addresses the compress() and decompress() functions, > but e.g. crc32() and adler32() are also touched by this issue. crc32() and adler32() were fixed by #10276. PyZlib_objcompress() and PyZlib_objdecompress() should be fixed. -- ___

[issue8650] zlibmodule.c isn't 64-bit clean

2011-02-21 Thread STINNER Victor
STINNER Victor added the comment: Woops, I removed a duplicate message of Antoine. in this issue instead of #8651. Removed message: - > Fixed by r87729. This only addresses the compress() and decompress() functions, but e.g. crc32() and adler32() are also touched by this issue. - ---

[issue8650] zlibmodule.c isn't 64-bit clean

2011-02-21 Thread STINNER Victor
Changes by STINNER Victor : -- Removed message: http://bugs.python.org/msg128975 ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8650] zlibmodule.c isn't 64-bit clean

2011-02-21 Thread Nadeem Vawda
Changes by Nadeem Vawda : -- nosy: +nvawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8650] zlibmodule.c isn't 64-bit clean

2011-02-21 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Fixed by r87729. This only addresses the compress() and decompress() functions, but e.g. crc32() and adler32() are also touched by this issue. -- versions: -Python 2.6, Python 3.1, Python 3.2 ___ Python tracker

[issue8650] zlibmodule.c isn't 64-bit clean

2011-01-03 Thread STINNER Victor
STINNER Victor added the comment: Fixed by r87729. Wait for the buildbots before backporting to other versions. -- ___ Python tracker ___ ___

[issue8650] zlibmodule.c isn't 64-bit clean

2010-08-15 Thread Martin v . Löwis
Changes by Martin v. Löwis : -- Removed message: http://bugs.python.org/msg113981 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue8650] zlibmodule.c isn't 64-bit clean

2010-08-15 Thread Martin v . Löwis
Martin v. Löwis added the comment: Using chunked writes is tricky. If the first write succeeds, and the second one fails, how do you report the result? -- nosy: +loewis ___ Python tracker _

[issue8650] zlibmodule.c isn't 64-bit clean

2010-05-29 Thread Ryan Coyner
Changes by Ryan Coyner : -- nosy: +rcoyner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8650] zlibmodule.c isn't 64-bit clean

2010-05-26 Thread STINNER Victor
STINNER Victor added the comment: See also a related issue: #8651. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue8650] zlibmodule.c isn't 64-bit clean

2010-05-07 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8650] zlibmodule.c isn't 64-bit clean

2010-05-07 Thread Antoine Pitrou
New submission from Antoine Pitrou : zlibmodule.c doesn't define PY_SSIZE_T_CLEAN, and uses lots of "int" variables for length values internally. Besides, the zlib itself uses "uInt" and "uLong" variables in its z_stream structure (rather than something guaranteed to be at least the width of a