http://bugs.python.org/review/14736/diff/4831/17094 File Modules/_lzmamodule.c (right): http://bugs.python.org/review/14736/diff/4831/17094#newcode1169 Modules/_lzmamodule.c:1169: /* XXX We use vanilla free() here instead of ...
http://bugs.python.org/review/14736/diff/4831/17094
File Modules/_lzmamodule.c (right):
http://bugs.python.org/review/14736/diff/4831/17094#newcode1169
Modules/_lzmamodule.c:1169: /* XXX We use vanilla free() here instead of
PyMem_Free(), since
On 2012/05/06 09:34:21, loewis wrote:
> Why is this an XXX comment? The API usage looks correct to me.
You're right, it's not necessary. Fixed.
> You could setup an LZMA allocator if you wanted to.
True, but it seems like a lot of added code for a cosmetic
matter - we'd have to define wrappers for PyMem_Malloc() and
PyMem_Free(), since the allocator API expects different
function signatures.
Issue 14736: Add {encode,decode}_filter_properties() functions to lzma module
Created 1 year ago by nadeem.vawda
Modified 1 year ago
Reviewers: loewis
Base URL: None
Comments: 2