Message291253
I'm not sure I agree with that. The docs for compressobj just say
"Returns a compression object, to be used for compressing data streams that won’t fit into memory at once."
Which I don't think says much about the complexity aspect. Whether you're compressing a smaller bit of data or a stream, I think the optional parameters in compressobj are just as applicable to compress. When you've got an in-memory chunk of data, it seems to be going out of the way to construct a compressobj just to get at the optional parameters. |
|
Date |
User |
Action |
Args |
2017-04-07 05:56:17 | Ellison Marks | set | recipients:
+ Ellison Marks, martin.panter, xiang.zhang |
2017-04-07 05:56:17 | Ellison Marks | set | messageid: <1491544577.16.0.336209946883.issue30000@psf.upfronthosting.co.za> |
2017-04-07 05:56:17 | Ellison Marks | link | issue30000 messages |
2017-04-07 05:56:16 | Ellison Marks | create | |
|