summaryrefslogtreecommitdiffstats
path: root/Lib/test/testtar.tar
diff options
context:
space:
mode:
authorLars Gustäbel <lars@gustaebel.de>2010-05-17 18:02:50 (GMT)
committerLars Gustäbel <lars@gustaebel.de>2010-05-17 18:02:50 (GMT)
commit1465cc2887be2054cca50c72ef804adcc15fdf65 (patch)
tree3f20bc90a15488fcbca7868415cf35d2bc1e114a /Lib/test/testtar.tar
parent0f78a94f445c48f5a96a77a1bb77ca88d7c50694 (diff)
downloadcpython-1465cc2887be2054cca50c72ef804adcc15fdf65.zip
cpython-1465cc2887be2054cca50c72ef804adcc15fdf65.tar.gz
cpython-1465cc2887be2054cca50c72ef804adcc15fdf65.tar.bz2
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 b5bb46b..c3022ed 100644
--- a/Lib/test/testtar.tar
+++ b/Lib/test/testtar.tar
Binary files differ