12.5.1 TarFile Objects
The TarFile object provides an interface to a tar archive. A tar
archive is a sequence of blocks. An archive member (a stored file) is made up
of a header block followed by data blocks. It is possible, to store a file in a
tar archive several times. Each archive member is represented by a
TarInfo object, see TarInfo Objects (section
12.5.2) for details.
[, mode[, fileobj]]])|
Open an (uncompressed) tar archive name.
mode is either
'r' to read from an existing archive,
'a' to append data to an existing file or
'w' to create a new
file overwriting an existing one. mode defaults to
If fileobj is given, it is used for reading or writing data.
If it can be determined, mode is overridden by fileobj's mode.
fileobj will be used from position 0.
fileobj is not closed, when TarFile is closed.
Alternative constructor. The open() function on module level is
actually a shortcut to this classmethod. See section 12.5
Return a TarInfo object for member name. If name can
not be found in the archive, KeyError is raised.
If a member occurs more than once in the archive, its last
occurrence is assumed to be the most up-to-date version.
Return the members of the archive as a list of TarInfo objects.
The list has the same order as the members in the archive.
Return the members as a list of their names. It has the same order as
the list returned by getmembers().
Print a table of contents to
sys.stdout. If verbose is
False, only the names of the members are printed. If it is
True, output similar to that of ls -l is produced.
Return the next member of the archive as a TarInfo object, when
TarFile is opened for reading. Return
None if there is no
Extract all members from the archive to the current working directory
or directory path. If optional members is given, it must be
a subset of the list returned by getmembers().
Directory informations like owner, modification time and permissions are
set after all members have been extracted. This is done to work around two
problems: A directory's modification time is reset each time a file is
created in it. And, if a directory's permissions do not allow writing,
extracting files to it will fail.
Never extract archives from untrusted sources without prior inspection.
It is possible that files are created outside of path, e.g. members
that have absolute filenames starting with
New in version 2.5.
"/" or filenames with
Extract a member from the archive to the current working directory,
using its full name. Its file information is extracted as accurately as
member may be a filename or a TarInfo object.
You can specify a different directory using path.
Because the extract() method allows random access to a tar
archive there are some issues you must take care of yourself. See the
description for extractall() above.
See the warning for extractall().
Extract a member from the archive as a file object.
member may be a filename or a TarInfo object.
If member is a regular file, a file-like object is returned.
If member is a link, a file-like object is constructed from the
If member is none of the above,
None is returned.
The file-like object is read-only and provides the following methods:
read(), readline(), readlines(),
||name[, arcname[, recursive]])|
Add the file name to the archive. name may be any type
of file (directory, fifo, symbolic link, etc.).
If given, arcname specifies an alternative name for the file in the
archive. Directories are added recursively by default.
This can be avoided by setting recursive to False;
the default is True.
Add the TarInfo object tarinfo to the archive.
If fileobj is given,
tarinfo.size bytes are read
from it and added to the archive. You can create TarInfo objects
On Windows platforms, fileobj should always be opened with mode
'rb' to avoid irritation about the file size.
Create a TarInfo object for either the file name or
the file object fileobj (using os.fstat() on its
file descriptor). You can modify some of the TarInfo's
attributes before you add it using addfile(). If given,
arcname specifies an alternative name for the file in the
Close the TarFile. In write mode, two finishing zero
blocks are appended to the archive.
If true, create a POSIX 1003.1-1990 compliant archive. GNU
extensions are not used, because they are not part of the POSIX
standard. This limits the length of filenames to at most 256,
link names to 100 characters and the maximum file size to 8
gigabytes. A ValueError is raised if a file exceeds
this limit. If false, create a GNU tar compatible archive. It
will not be POSIX compliant, but can store files without any
of the above restrictions.
Changed in version 2.4:
posix defaults to False.
If false, add symbolic and hard links to archive. If true, add the
content of the target files to the archive. This has no effect on
systems that do not support symbolic links.
If false, treat an empty block as the end of the archive. If true,
skip empty (and invalid) blocks and try to get as many members as
possible. This is only useful for concatenated or damaged
To be set from
0 (no debug messages; the default) up to
3 (all debug messages). The messages are written to
0 (the default), all errors are ignored when using
extract(). Nevertheless, they appear as error messages
in the debug output, when debugging is enabled. If
fatal errors are raised as OSError or
IOError exceptions. If
2, all non-fatal
errors are raised as TarError exceptions as well.
See About this document... for information on suggesting changes.