调试Python的zlib和golang的zlib之间的差异。为什么以下结果不一样?
compress.go
:
package main
import (
"compress/flate"
"bytes"
"fmt"
)
func compress(source string) []byte {
w, _ := flate.NewWriter(nil, 7)
buf := new(bytes.Buffer)
w.Reset(buf)
w.Write([]byte(source))
w.Close()
return buf.Bytes()
}
func main() {
example := "foo"
compressed := compress(example)
fmt.Println(compressed)
}
compress.py
:
from __future__ import print_function
import zlib
def compress(source):
# golang zlib strips header + checksum
compressor = zlib.compressobj(7, zlib.DEFLATED, -15)
compressor.compress(source)
# python zlib defaults to Z_FLUSH, but
# https://golang.org/pkg/compress/flate/#Writer.Flush
# says "Flush is equivalent to Z_SYNC_FLUSH"
return compressor.flush(zlib.Z_SYNC_FLUSH)
def main():
example = u"foo"
compressed = compress(example)
print(list(bytearray(compressed)))
if __name__ == "__main__":
main()
结果
$ go version
go version go1.7.3 darwin/amd64
$ go build compress.go
$ ./compress
[74 203 207 7 4 0 0 255 255]
$ python --version
$ python 2.7.12
$ python compress.py
[74, 203, 207, 7, 0, 0, 0, 255, 255]
Python版本的第五个字节有0
,但golang版本有4
- 导致不同输出的是什么?
答案 0 :(得分:2)
python示例的输出不是"完成"流,它只是在压缩第一个字符串后刷新缓冲区。通过将Close()
替换为Flush()
:
https://play.golang.org/p/BMcjTln-ej
func compress(source string) []byte {
buf := new(bytes.Buffer)
w, _ := flate.NewWriter(buf, 7)
w.Write([]byte(source))
w.Flush()
return buf.Bytes()
}
但是,您要比较python中zlib的输出,它在内部使用DEFLATE生成zlib格式输出,在Go中使用flate
,其中是 DEFLATE实现。我不知道你是否可以让python zlib库输出原始的,完整的DEFLATE流,但试图让不同的库输出压缩数据的逐字节匹配似乎没有用或可维护。压缩库的输出仅保证兼容,不相同。