3 :mod:`tarfile` --- Read and write tar archive files
4 ===================================================
7 :synopsis: Read and write tar-format archive files.
12 .. moduleauthor:: Lars Gustäbel <lars@gustaebel.de>
13 .. sectionauthor:: Lars Gustäbel <lars@gustaebel.de>
16 The :mod:`tarfile` module makes it possible to read and write tar
17 archives, including those using gzip or bz2 compression.
18 (:file:`.zip` files can be read and written using the :mod:`zipfile` module.)
20 Some facts and figures:
22 * reads and writes :mod:`gzip` and :mod:`bz2` compressed archives.
24 * read/write support for the POSIX.1-1988 (ustar) format.
26 * read/write support for the GNU tar format including *longname* and *longlink*
27 extensions, read-only support for the *sparse* extension.
29 * read/write support for the POSIX.1-2001 (pax) format.
33 * handles directories, regular files, hardlinks, symbolic links, fifos,
34 character devices and block devices and is able to acquire and restore file
35 information like timestamp, access permissions and owner.
38 .. function:: open(name=None, mode='r', fileobj=None, bufsize=10240, \*\*kwargs)
40 Return a :class:`TarFile` object for the pathname *name*. For detailed
41 information on :class:`TarFile` objects and the keyword arguments that are
42 allowed, see :ref:`tarfile-objects`.
44 *mode* has to be a string of the form ``'filemode[:compression]'``, it defaults
45 to ``'r'``. Here is a full list of mode combinations:
47 +------------------+---------------------------------------------+
49 +==================+=============================================+
50 | ``'r' or 'r:*'`` | Open for reading with transparent |
51 | | compression (recommended). |
52 +------------------+---------------------------------------------+
53 | ``'r:'`` | Open for reading exclusively without |
55 +------------------+---------------------------------------------+
56 | ``'r:gz'`` | Open for reading with gzip compression. |
57 +------------------+---------------------------------------------+
58 | ``'r:bz2'`` | Open for reading with bzip2 compression. |
59 +------------------+---------------------------------------------+
60 | ``'a' or 'a:'`` | Open for appending with no compression. The |
61 | | file is created if it does not exist. |
62 +------------------+---------------------------------------------+
63 | ``'w' or 'w:'`` | Open for uncompressed writing. |
64 +------------------+---------------------------------------------+
65 | ``'w:gz'`` | Open for gzip compressed writing. |
66 +------------------+---------------------------------------------+
67 | ``'w:bz2'`` | Open for bzip2 compressed writing. |
68 +------------------+---------------------------------------------+
70 Note that ``'a:gz'`` or ``'a:bz2'`` is not possible. If *mode* is not suitable
71 to open a certain (compressed) file for reading, :exc:`ReadError` is raised. Use
72 *mode* ``'r'`` to avoid this. If a compression method is not supported,
73 :exc:`CompressionError` is raised.
75 If *fileobj* is specified, it is used as an alternative to a file object opened
76 for *name*. It is supposed to be at position 0.
78 For special purposes, there is a second format for *mode*:
79 ``'filemode|[compression]'``. :func:`tarfile.open` will return a :class:`TarFile`
80 object that processes its data as a stream of blocks. No random seeking will
81 be done on the file. If given, *fileobj* may be any object that has a
82 :meth:`read` or :meth:`write` method (depending on the *mode*). *bufsize*
83 specifies the blocksize and defaults to ``20 * 512`` bytes. Use this variant
84 in combination with e.g. ``sys.stdin``, a socket file object or a tape
85 device. However, such a :class:`TarFile` object is limited in that it does
86 not allow to be accessed randomly, see :ref:`tar-examples`. The currently
89 +-------------+--------------------------------------------+
91 +=============+============================================+
92 | ``'r|*'`` | Open a *stream* of tar blocks for reading |
93 | | with transparent compression. |
94 +-------------+--------------------------------------------+
95 | ``'r|'`` | Open a *stream* of uncompressed tar blocks |
97 +-------------+--------------------------------------------+
98 | ``'r|gz'`` | Open a gzip compressed *stream* for |
100 +-------------+--------------------------------------------+
101 | ``'r|bz2'`` | Open a bzip2 compressed *stream* for |
103 +-------------+--------------------------------------------+
104 | ``'w|'`` | Open an uncompressed *stream* for writing. |
105 +-------------+--------------------------------------------+
106 | ``'w|gz'`` | Open an gzip compressed *stream* for |
108 +-------------+--------------------------------------------+
109 | ``'w|bz2'`` | Open an bzip2 compressed *stream* for |
111 +-------------+--------------------------------------------+
116 Class for reading and writing tar archives. Do not use this class directly,
117 better use :func:`tarfile.open` instead. See :ref:`tarfile-objects`.
120 .. function:: is_tarfile(name)
122 Return :const:`True` if *name* is a tar archive file, that the :mod:`tarfile`
126 .. class:: TarFileCompat(filename, mode='r', compression=TAR_PLAIN)
128 Class for limited access to tar archives with a :mod:`zipfile`\ -like interface.
129 Please consult the documentation of the :mod:`zipfile` module for more details.
130 *compression* must be one of the following constants:
135 Constant for an uncompressed tar archive.
138 .. data:: TAR_GZIPPED
140 Constant for a :mod:`gzip` compressed tar archive.
144 The :class:`TarFileCompat` class has been deprecated for removal in Python 3.0.
147 .. exception:: TarError
149 Base class for all :mod:`tarfile` exceptions.
152 .. exception:: ReadError
154 Is raised when a tar archive is opened, that either cannot be handled by the
155 :mod:`tarfile` module or is somehow invalid.
158 .. exception:: CompressionError
160 Is raised when a compression method is not supported or when the data cannot be
164 .. exception:: StreamError
166 Is raised for the limitations that are typical for stream-like :class:`TarFile`
170 .. exception:: ExtractError
172 Is raised for *non-fatal* errors when using :meth:`TarFile.extract`, but only if
173 :attr:`TarFile.errorlevel`\ ``== 2``.
176 .. exception:: HeaderError
178 Is raised by :meth:`TarInfo.frombuf` if the buffer it gets is invalid.
180 .. versionadded:: 2.6
183 Each of the following constants defines a tar archive format that the
184 :mod:`tarfile` module is able to create. See section :ref:`tar-formats` for
188 .. data:: USTAR_FORMAT
190 POSIX.1-1988 (ustar) format.
200 POSIX.1-2001 (pax) format.
203 .. data:: DEFAULT_FORMAT
205 The default format for creating archives. This is currently :const:`GNU_FORMAT`.
208 The following variables are available on module level:
213 The default character encoding i.e. the value from either
214 :func:`sys.getfilesystemencoding` or :func:`sys.getdefaultencoding`.
219 Module :mod:`zipfile`
220 Documentation of the :mod:`zipfile` standard module.
222 `GNU tar manual, Basic Tar Format <http://www.gnu.org/software/tar/manual/html_node/Standard.html>`_
223 Documentation for tar archive files, including GNU tar extensions.
231 The :class:`TarFile` object provides an interface to a tar archive. A tar
232 archive is a sequence of blocks. An archive member (a stored file) is made up of
233 a header block followed by data blocks. It is possible to store a file in a tar
234 archive several times. Each archive member is represented by a :class:`TarInfo`
235 object, see :ref:`tarinfo-objects` for details.
238 .. class:: TarFile(name=None, mode='r', fileobj=None, format=DEFAULT_FORMAT, tarinfo=TarInfo, dereference=False, ignore_zeros=False, encoding=ENCODING, errors=None, pax_headers=None, debug=0, errorlevel=0)
240 All following arguments are optional and can be accessed as instance attributes
243 *name* is the pathname of the archive. It can be omitted if *fileobj* is given.
244 In this case, the file object's :attr:`name` attribute is used if it exists.
246 *mode* is either ``'r'`` to read from an existing archive, ``'a'`` to append
247 data to an existing file or ``'w'`` to create a new file overwriting an existing
250 If *fileobj* is given, it is used for reading or writing data. If it can be
251 determined, *mode* is overridden by *fileobj*'s mode. *fileobj* will be used
256 *fileobj* is not closed, when :class:`TarFile` is closed.
258 *format* controls the archive format. It must be one of the constants
259 :const:`USTAR_FORMAT`, :const:`GNU_FORMAT` or :const:`PAX_FORMAT` that are
260 defined at module level.
262 .. versionadded:: 2.6
264 The *tarinfo* argument can be used to replace the default :class:`TarInfo` class
265 with a different one.
267 .. versionadded:: 2.6
269 If *dereference* is :const:`False`, add symbolic and hard links to the archive. If it
270 is :const:`True`, add the content of the target files to the archive. This has no
271 effect on systems that do not support symbolic links.
273 If *ignore_zeros* is :const:`False`, treat an empty block as the end of the archive.
274 If it is :const:`True`, skip empty (and invalid) blocks and try to get as many members
275 as possible. This is only useful for reading concatenated or damaged archives.
277 *debug* can be set from ``0`` (no debug messages) up to ``3`` (all debug
278 messages). The messages are written to ``sys.stderr``.
280 If *errorlevel* is ``0``, all errors are ignored when using :meth:`TarFile.extract`.
281 Nevertheless, they appear as error messages in the debug output, when debugging
282 is enabled. If ``1``, all *fatal* errors are raised as :exc:`OSError` or
283 :exc:`IOError` exceptions. If ``2``, all *non-fatal* errors are raised as
284 :exc:`TarError` exceptions as well.
286 The *encoding* and *errors* arguments control the way strings are converted to
287 unicode objects and vice versa. The default settings will work for most users.
288 See section :ref:`tar-unicode` for in-depth information.
290 .. versionadded:: 2.6
292 The *pax_headers* argument is an optional dictionary of unicode strings which
293 will be added as a pax global header if *format* is :const:`PAX_FORMAT`.
295 .. versionadded:: 2.6
298 .. method:: TarFile.open(...)
300 Alternative constructor. The :func:`tarfile.open` function is actually a
301 shortcut to this classmethod.
304 .. method:: TarFile.getmember(name)
306 Return a :class:`TarInfo` object for member *name*. If *name* can not be found
307 in the archive, :exc:`KeyError` is raised.
311 If a member occurs more than once in the archive, its last occurrence is assumed
312 to be the most up-to-date version.
315 .. method:: TarFile.getmembers()
317 Return the members of the archive as a list of :class:`TarInfo` objects. The
318 list has the same order as the members in the archive.
321 .. method:: TarFile.getnames()
323 Return the members as a list of their names. It has the same order as the list
324 returned by :meth:`getmembers`.
327 .. method:: TarFile.list(verbose=True)
329 Print a table of contents to ``sys.stdout``. If *verbose* is :const:`False`,
330 only the names of the members are printed. If it is :const:`True`, output
331 similar to that of :program:`ls -l` is produced.
334 .. method:: TarFile.next()
336 Return the next member of the archive as a :class:`TarInfo` object, when
337 :class:`TarFile` is opened for reading. Return :const:`None` if there is no more
341 .. method:: TarFile.extractall(path=".", members=None)
343 Extract all members from the archive to the current working directory or
344 directory *path*. If optional *members* is given, it must be a subset of the
345 list returned by :meth:`getmembers`. Directory information like owner,
346 modification time and permissions are set after all members have been extracted.
347 This is done to work around two problems: A directory's modification time is
348 reset each time a file is created in it. And, if a directory's permissions do
349 not allow writing, extracting files to it will fail.
353 Never extract archives from untrusted sources without prior inspection.
354 It is possible that files are created outside of *path*, e.g. members
355 that have absolute filenames starting with ``"/"`` or filenames with two
358 .. versionadded:: 2.5
361 .. method:: TarFile.extract(member, path="")
363 Extract a member from the archive to the current working directory, using its
364 full name. Its file information is extracted as accurately as possible. *member*
365 may be a filename or a :class:`TarInfo` object. You can specify a different
366 directory using *path*.
370 The :meth:`extract` method does not take care of several extraction issues.
371 In most cases you should consider using the :meth:`extractall` method.
375 See the warning for :meth:`extractall`.
378 .. method:: TarFile.extractfile(member)
380 Extract a member from the archive as a file object. *member* may be a filename
381 or a :class:`TarInfo` object. If *member* is a regular file, a file-like object
382 is returned. If *member* is a link, a file-like object is constructed from the
383 link's target. If *member* is none of the above, :const:`None` is returned.
387 The file-like object is read-only. It provides the methods
388 :meth:`read`, :meth:`readline`, :meth:`readlines`, :meth:`seek`, :meth:`tell`,
389 and :meth:`close`, and also supports iteration over its lines.
392 .. method:: TarFile.add(name, arcname=None, recursive=True, exclude=None, filter=None)
394 Add the file *name* to the archive. *name* may be any type of file (directory,
395 fifo, symbolic link, etc.). If given, *arcname* specifies an alternative name
396 for the file in the archive. Directories are added recursively by default. This
397 can be avoided by setting *recursive* to :const:`False`. If *exclude* is given
398 it must be a function that takes one filename argument and returns a boolean
399 value. Depending on this value the respective file is either excluded
400 (:const:`True`) or added (:const:`False`). If *filter* is specified it must
401 be a function that takes a :class:`TarInfo` object argument and returns the
402 changed :class:`TarInfo` object. If it instead returns :const:`None` the :class:`TarInfo`
403 object will be excluded from the archive. See :ref:`tar-examples` for an
406 .. versionchanged:: 2.6
407 Added the *exclude* parameter.
409 .. versionchanged:: 2.7
410 Added the *filter* parameter.
413 The *exclude* parameter is deprecated, please use the *filter* parameter
417 .. method:: TarFile.addfile(tarinfo, fileobj=None)
419 Add the :class:`TarInfo` object *tarinfo* to the archive. If *fileobj* is given,
420 ``tarinfo.size`` bytes are read from it and added to the archive. You can
421 create :class:`TarInfo` objects using :meth:`gettarinfo`.
425 On Windows platforms, *fileobj* should always be opened with mode ``'rb'`` to
426 avoid irritation about the file size.
429 .. method:: TarFile.gettarinfo(name=None, arcname=None, fileobj=None)
431 Create a :class:`TarInfo` object for either the file *name* or the file object
432 *fileobj* (using :func:`os.fstat` on its file descriptor). You can modify some
433 of the :class:`TarInfo`'s attributes before you add it using :meth:`addfile`.
434 If given, *arcname* specifies an alternative name for the file in the archive.
437 .. method:: TarFile.close()
439 Close the :class:`TarFile`. In write mode, two finishing zero blocks are
440 appended to the archive.
443 .. attribute:: TarFile.posix
445 Setting this to :const:`True` is equivalent to setting the :attr:`format`
446 attribute to :const:`USTAR_FORMAT`, :const:`False` is equivalent to
449 .. versionchanged:: 2.4
450 *posix* defaults to :const:`False`.
453 Use the :attr:`format` attribute instead.
456 .. attribute:: TarFile.pax_headers
458 A dictionary containing key-value pairs of pax global headers.
460 .. versionadded:: 2.6
468 A :class:`TarInfo` object represents one member in a :class:`TarFile`. Aside
469 from storing all required attributes of a file (like file type, size, time,
470 permissions, owner etc.), it provides some useful methods to determine its type.
471 It does *not* contain the file's data itself.
473 :class:`TarInfo` objects are returned by :class:`TarFile`'s methods
474 :meth:`getmember`, :meth:`getmembers` and :meth:`gettarinfo`.
477 .. class:: TarInfo(name="")
479 Create a :class:`TarInfo` object.
482 .. method:: TarInfo.frombuf(buf)
484 Create and return a :class:`TarInfo` object from string buffer *buf*.
486 .. versionadded:: 2.6
487 Raises :exc:`HeaderError` if the buffer is invalid..
490 .. method:: TarInfo.fromtarfile(tarfile)
492 Read the next member from the :class:`TarFile` object *tarfile* and return it as
493 a :class:`TarInfo` object.
495 .. versionadded:: 2.6
498 .. method:: TarInfo.tobuf(format=DEFAULT_FORMAT, encoding=ENCODING, errors='strict')
500 Create a string buffer from a :class:`TarInfo` object. For information on the
501 arguments see the constructor of the :class:`TarFile` class.
503 .. versionchanged:: 2.6
504 The arguments were added.
506 A ``TarInfo`` object has the following public data attributes:
509 .. attribute:: TarInfo.name
511 Name of the archive member.
514 .. attribute:: TarInfo.size
519 .. attribute:: TarInfo.mtime
521 Time of last modification.
524 .. attribute:: TarInfo.mode
529 .. attribute:: TarInfo.type
531 File type. *type* is usually one of these constants: :const:`REGTYPE`,
532 :const:`AREGTYPE`, :const:`LNKTYPE`, :const:`SYMTYPE`, :const:`DIRTYPE`,
533 :const:`FIFOTYPE`, :const:`CONTTYPE`, :const:`CHRTYPE`, :const:`BLKTYPE`,
534 :const:`GNUTYPE_SPARSE`. To determine the type of a :class:`TarInfo` object
535 more conveniently, use the ``is_*()`` methods below.
538 .. attribute:: TarInfo.linkname
540 Name of the target file name, which is only present in :class:`TarInfo` objects
541 of type :const:`LNKTYPE` and :const:`SYMTYPE`.
544 .. attribute:: TarInfo.uid
546 User ID of the user who originally stored this member.
549 .. attribute:: TarInfo.gid
551 Group ID of the user who originally stored this member.
554 .. attribute:: TarInfo.uname
559 .. attribute:: TarInfo.gname
564 .. attribute:: TarInfo.pax_headers
566 A dictionary containing key-value pairs of an associated pax extended header.
568 .. versionadded:: 2.6
570 A :class:`TarInfo` object also provides some convenient query methods:
573 .. method:: TarInfo.isfile()
575 Return :const:`True` if the :class:`Tarinfo` object is a regular file.
578 .. method:: TarInfo.isreg()
580 Same as :meth:`isfile`.
583 .. method:: TarInfo.isdir()
585 Return :const:`True` if it is a directory.
588 .. method:: TarInfo.issym()
590 Return :const:`True` if it is a symbolic link.
593 .. method:: TarInfo.islnk()
595 Return :const:`True` if it is a hard link.
598 .. method:: TarInfo.ischr()
600 Return :const:`True` if it is a character device.
603 .. method:: TarInfo.isblk()
605 Return :const:`True` if it is a block device.
608 .. method:: TarInfo.isfifo()
610 Return :const:`True` if it is a FIFO.
613 .. method:: TarInfo.isdev()
615 Return :const:`True` if it is one of character device, block device or FIFO.
623 How to extract an entire tar archive to the current working directory::
626 tar = tarfile.open("sample.tar.gz")
630 How to extract a subset of a tar archive with :meth:`TarFile.extractall` using
631 a generator function instead of a list::
636 def py_files(members):
637 for tarinfo in members:
638 if os.path.splitext(tarinfo.name)[1] == ".py":
641 tar = tarfile.open("sample.tar.gz")
642 tar.extractall(members=py_files(tar))
645 How to create an uncompressed tar archive from a list of filenames::
648 tar = tarfile.open("sample.tar", "w")
649 for name in ["foo", "bar", "quux"]:
653 How to read a gzip compressed tar archive and display some member information::
656 tar = tarfile.open("sample.tar.gz", "r:gz")
658 print tarinfo.name, "is", tarinfo.size, "bytes in size and is",
660 print "a regular file."
661 elif tarinfo.isdir():
664 print "something else."
667 How to create an archive and reset the user information using the *filter*
668 parameter in :meth:`TarFile.add`::
672 tarinfo.uid = tarinfo.gid = 0
673 tarinfo.uname = tarinfo.gname = "root"
675 tar = tarfile.open("sample.tar.gz", "w:gz")
676 tar.add("foo", filter=reset)
682 Supported tar formats
683 ---------------------
685 There are three tar formats that can be created with the :mod:`tarfile` module:
687 * The POSIX.1-1988 ustar format (:const:`USTAR_FORMAT`). It supports filenames
688 up to a length of at best 256 characters and linknames up to 100 characters. The
689 maximum file size is 8 gigabytes. This is an old and limited but widely
692 * The GNU tar format (:const:`GNU_FORMAT`). It supports long filenames and
693 linknames, files bigger than 8 gigabytes and sparse files. It is the de facto
694 standard on GNU/Linux systems. :mod:`tarfile` fully supports the GNU tar
695 extensions for long names, sparse file support is read-only.
697 * The POSIX.1-2001 pax format (:const:`PAX_FORMAT`). It is the most flexible
698 format with virtually no limits. It supports long filenames and linknames, large
699 files and stores pathnames in a portable way. However, not all tar
700 implementations today are able to handle pax archives properly.
702 The *pax* format is an extension to the existing *ustar* format. It uses extra
703 headers for information that cannot be stored otherwise. There are two flavours
704 of pax headers: Extended headers only affect the subsequent file header, global
705 headers are valid for the complete archive and affect all following files. All
706 the data in a pax header is encoded in *UTF-8* for portability reasons.
708 There are some more variants of the tar format which can be read, but not
711 * The ancient V7 format. This is the first tar format from Unix Seventh Edition,
712 storing only regular files and directories. Names must not be longer than 100
713 characters, there is no user/group name information. Some archives have
714 miscalculated header checksums in case of fields with non-ASCII characters.
716 * The SunOS tar extended format. This format is a variant of the POSIX.1-2001
717 pax format, but is not compatible.
724 The tar format was originally conceived to make backups on tape drives with the
725 main focus on preserving file system information. Nowadays tar archives are
726 commonly used for file distribution and exchanging archives over networks. One
727 problem of the original format (that all other formats are merely variants of)
728 is that there is no concept of supporting different character encodings. For
729 example, an ordinary tar archive created on a *UTF-8* system cannot be read
730 correctly on a *Latin-1* system if it contains non-ASCII characters. Names (i.e.
731 filenames, linknames, user/group names) containing these characters will appear
732 damaged. Unfortunately, there is no way to autodetect the encoding of an
735 The pax format was designed to solve this problem. It stores non-ASCII names
736 using the universal character encoding *UTF-8*. When a pax archive is read,
737 these *UTF-8* names are converted to the encoding of the local file system.
739 The details of unicode conversion are controlled by the *encoding* and *errors*
740 keyword arguments of the :class:`TarFile` class.
742 The default value for *encoding* is the local character encoding. It is deduced
743 from :func:`sys.getfilesystemencoding` and :func:`sys.getdefaultencoding`. In
744 read mode, *encoding* is used exclusively to convert unicode names from a pax
745 archive to strings in the local character encoding. In write mode, the use of
746 *encoding* depends on the chosen archive format. In case of :const:`PAX_FORMAT`,
747 input names that contain non-ASCII characters need to be decoded before being
748 stored as *UTF-8* strings. The other formats do not make use of *encoding*
749 unless unicode objects are used as input names. These are converted to 8-bit
750 character strings before they are added to the archive.
752 The *errors* argument defines how characters are treated that cannot be
753 converted to or from *encoding*. Possible values are listed in section
754 :ref:`codec-base-classes`. In read mode, there is an additional scheme
755 ``'utf-8'`` which means that bad characters are replaced by their *UTF-8*
756 representation. This is the default scheme. In write mode the default value for
757 *errors* is ``'strict'`` to ensure that name information is not altered