diff options
| author | Lars Gustäbel <lars@gustaebel.de> | 2010-05-17 18:02:50 (GMT) |
|---|---|---|
| committer | Lars Gustäbel <lars@gustaebel.de> | 2010-05-17 18:02:50 (GMT) |
| commit | 1465cc2887be2054cca50c72ef804adcc15fdf65 (patch) | |
| tree | 3f20bc90a15488fcbca7868415cf35d2bc1e114a /Misc | |
| parent | 0f78a94f445c48f5a96a77a1bb77ca88d7c50694 (diff) | |
| download | cpython-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 'Misc')
| -rw-r--r-- | Misc/NEWS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -366,6 +366,9 @@ C-API Library ------- +- Issue #8633: tarfile is now able to read and write archives with "raw" binary + pax headers as described in POSIX.1-2008. + - Issue #1285086: Speed up urllib.parse functions: quote, quote_from_bytes, unquote, unquote_to_bytes. |