[issue8633] tarfile doesn't support undecodable filename in PAX format

Lars Gustäbel added the comment: I added support for the hdrcharset method and a workaround for the GNU tar bug, see r81273. -- resolution: -> accepted status: open -> closed ___ Python tracker __

[issue8633] tarfile doesn't support undecodable filename in PAX format

Changes by Lars Gustäbel : -- assignee: -> lars.gustaebel ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue8633] tarfile doesn't support undecodable filename in PAX format

Lars Gustäbel added the comment: I am currently working on a patch to let tarfile use the hdrcharset field. -- ___ Python tracker ___

[issue8633] tarfile doesn't support undecodable filename in PAX format

Lars Gustäbel added the comment: Victor, you misunderstood the pax definition, but it wouldn't harm tarfile if it knew how to handle these corrupt GNU tar archives. In the meantime I filed a bug report on bug-...@gnu.org for this. I said in msg105085 that POSIX gives no advice on how to handl

[issue8633] tarfile doesn't support undecodable filename in PAX format

STINNER Victor added the comment: I didn't read the whole spec, only read quickly the invalid option. The idead behind this issue is to be able to read a file generated by GNU tar which keeps the filename unchanged if it's not encodable to utf8. (z-pax.tar attachment was generated by GNU tar)

[issue8633] tarfile doesn't support undecodable filename in PAX format

Martin v. Löwis added the comment: I think you are misinterpreting the spec. A PAX file MUST encode its file names in UTF-8. The "invalid" flag only applies when these invalid names cannot map to file names - either because they are not supported in the locale, or because they are not support

[issue8633] tarfile doesn't support undecodable filename in PAX format

New submission from STINNER Victor : tarfile is unable to open a TAR archive in PAX format embedding invalid filenames (filename not encoded in utf8, an undecodable filename). Attached file is an example (contain the file b'z/\xff', not decodable from utf8). PAX specification has a "invalid" o