summaryrefslogtreecommitdiff
path: root/Lib/test/testtar.tar
diff options
context:
space:
mode:
authorLars Gustäbel <lars@gustaebel.de>2010-05-17 18:02:50 +0000
committerLars Gustäbel <lars@gustaebel.de>2010-05-17 18:02:50 +0000
commitd4ad7546b2d21099ac1ac7e7121045cd40854ff7 (patch)
treeb67ce228b8f6da67575f005ba9c023978a058480 /Lib/test/testtar.tar
parent028e57b46b66ed393cf96aee3cd4d6ab4118068c (diff)
downloadcpython-d4ad7546b2d21099ac1ac7e7121045cd40854ff7.tar.gz
Issue #8633: Support for POSIX.1-2008 binary pax headers.
tarfile is now able to read and write pax headers with a "hdrcharset=BINARY" record. This record was introduced in POSIX.1-2008 as a method to store unencoded binary strings that cannot be translated to UTF-8. In practice, this is just a workaround that allows a tar implementation to store filenames that do not comply with the current filesystem encoding and thus cannot be decoded correctly. Additionally, tarfile works around a bug in current versions of GNU tar: undecodable filenames are stored as-is in a pax header without a "hdrcharset" record being added. Technically, these headers are invalid, but tarfile manages to read them correctly anyway.
Diffstat (limited to 'Lib/test/testtar.tar')
-rw-r--r--Lib/test/testtar.tarbin272384 -> 289792 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/Lib/test/testtar.tar b/Lib/test/testtar.tar
index b5bb46b16e..c3022ed196 100644
--- a/Lib/test/testtar.tar
+++ b/Lib/test/testtar.tar
Binary files differ