Skip to content
Discussion options

You must be logged in to vote

Both are intentional. zip/ is a fork of the standard library's archive/zip, and its testdata holds the fixtures from Go's own zip tests. test-prefix.zip is a valid archive with the text "prefix that could be an executable jar file" in front of it, used to test zips that don't start with PK (the test-prefix.zip case in zip/reader_test.go), and Python's zipfile opens it fine. There's no package without test data: GitHub builds the "Source code" zip of a release from the whole tagged tree, and the module zip that go mod download gets from proxy.golang.org has the same zip/testdata files. A few other fixtures there are odd on purpose too, like test-trailing-junk.zip and test-badbase.zip, so a…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@MrZoller
Comment options

@junkerderprovinz
Comment options

Answer selected by klauspost
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants