Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2455)

#14736: Add {encode,decode}_filter_properties() functions to lzma module

Can't Edit
Can't Publish+Mail
Start Review
Created:
1 year ago by nadeem.vawda
Modified:
1 year ago
Reviewers:
martin
CC:
AntoinePitrou, nadeem.vawda, storchaka
Visibility:
Public.

Patch Set 1 #

Total comments: 2

Patch Set 2 #

Unified diffs Side-by-side diffs Delta from patch set Stats Patch
Doc/library/lzma.rst View 1 chunk +26 lines, -0 lines 0 comments Download
Lib/lzma.py View 1 chunk +1 line, -0 lines 0 comments Download
Lib/test/test_lzma.py View 1 chunk +43 lines, -0 lines 0 comments Download
Modules/_lzmamodule.c View 1 5 chunks +182 lines, -4 lines 0 comments Download

Messages

Total messages: 2
loewis
The patch looks fine to me, except for the comment issue below. http://bugs.python.org/review/14736/diff/4831/17094 File Modules/_lzmamodule.c ...
1 year ago #1
nadeem.vawda
1 year ago #2
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.
Sign in to reply to this message.

RSS Feeds Recent Issues | This issue
This is Rietveld cbc36f91f3f7