This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients Sreejith.Madhavan, ddmitriev, gregory.p.smith, pitrou
Date 2010-05-07.16:26:27
SpamBayes Score 0.0002195008
Marked as misclassified No
Message-id <x2j52dc1c821005070926ifc8d463ehfe5651b209d3263c@mail.gmail.com>
In-reply-to <1273247759.82.0.945847578057.issue8571@psf.upfronthosting.co.za>
Content
in the unittests there is some use of 'compress' and 'decompress'
mixed with 'zlib.decompress'.  which one is right (i'm only looking at
the diff so i can't see if they were imported from zlib or if the
zlib. is required at the moment).

otherwise, provided the new bigmem tests pass.  looks good to me.
commit and backport through to 2.6.

On Fri, May 7, 2010 at 8:56 AM, Antoine Pitrou <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> Here is a patch fixing the issue, and a similar one in compressobj.compress(). It also adds tests which are only enabled with the bigmem option.
>
> ----------
> Added file: http://bugs.python.org/file17245/zlibbigbuf.patch
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue8571>
> _______________________________________
>
History
Date User Action Args
2010-05-07 16:26:30gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, Sreejith.Madhavan, ddmitriev
2010-05-07 16:26:28gregory.p.smithlinkissue8571 messages
2010-05-07 16:26:27gregory.p.smithcreate