summaryrefslogtreecommitdiffstats
path: root/Lib/plat-freebsd7
diff options
context:
space:
mode:
authorLars Gustäbel <lars@gustaebel.de>2010-05-17 18:11:22 (GMT)
committerLars Gustäbel <lars@gustaebel.de>2010-05-17 18:11:22 (GMT)
commit3a5d703045ebfebf45fdc1a26ac4c230c4773c45 (patch)
treeee0bd24631edcb30c0a94ab97d22026f085bb8bb /Lib/plat-freebsd7
parentdf47ffd773efc8fc78ffc3354fc8630d84226503 (diff)
downloadcpython-3a5d703045ebfebf45fdc1a26ac4c230c4773c45.zip
cpython-3a5d703045ebfebf45fdc1a26ac4c230c4773c45.tar.gz
cpython-3a5d703045ebfebf45fdc1a26ac4c230c4773c45.tar.bz2
Blocked revisions 81273 via svnmerge
........ r81273 | lars.gustaebel | 2010-05-17 20:02:50 +0200 (Mon, 17 May 2010) | 15 lines 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/plat-freebsd7')
0 files changed, 0 insertions, 0 deletions