blob: b62148aead1382cc2c04c9577ad28eca7de61836 [file] [log] [blame]
Georg Brandl8ec7f652007-08-15 14:28:01 +00001.. _tarfile-mod:
2
3:mod:`tarfile` --- Read and write tar archive files
4===================================================
5
6.. module:: tarfile
7 :synopsis: Read and write tar-format archive files.
8
9
10.. versionadded:: 2.3
11
12.. moduleauthor:: Lars Gustäbel <lars@gustaebel.de>
13.. sectionauthor:: Lars Gustäbel <lars@gustaebel.de>
14
15
Mark Summerfieldaea6e592007-11-05 09:22:48 +000016The :mod:`tarfile` module makes it possible to read and write tar
17archives, including those using gzip or bz2 compression.
Georg Brandl2b92f6b2007-12-06 01:52:24 +000018(:file:`.zip` files can be read and written using the :mod:`zipfile` module.)
Mark Summerfieldaea6e592007-11-05 09:22:48 +000019
Georg Brandl8ec7f652007-08-15 14:28:01 +000020Some facts and figures:
21
Mark Summerfieldaea6e592007-11-05 09:22:48 +000022* reads and writes :mod:`gzip` and :mod:`bz2` compressed archives.
Georg Brandl8ec7f652007-08-15 14:28:01 +000023
24* read/write support for the POSIX.1-1988 (ustar) format.
25
26* read/write support for the GNU tar format including *longname* and *longlink*
27 extensions, read-only support for the *sparse* extension.
28
29* read/write support for the POSIX.1-2001 (pax) format.
30
31 .. versionadded:: 2.6
32
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.
36
Georg Brandl8ec7f652007-08-15 14:28:01 +000037
Lars Gustäbel4bfb5932008-05-17 16:50:22 +000038.. function:: open(name=None, mode='r', fileobj=None, bufsize=10240, \*\*kwargs)
Georg Brandl8ec7f652007-08-15 14:28:01 +000039
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`.
43
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:
46
47 +------------------+---------------------------------------------+
48 | mode | action |
49 +==================+=============================================+
50 | ``'r' or 'r:*'`` | Open for reading with transparent |
51 | | compression (recommended). |
52 +------------------+---------------------------------------------+
53 | ``'r:'`` | Open for reading exclusively without |
54 | | compression. |
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 +------------------+---------------------------------------------+
69
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.
74
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.
77
78 For special purposes, there is a second format for *mode*:
Lars Gustäbel4bfb5932008-05-17 16:50:22 +000079 ``'filemode|[compression]'``. :func:`tarfile.open` will return a :class:`TarFile`
Georg Brandl8ec7f652007-08-15 14:28:01 +000080 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
87 possible modes:
88
89 +-------------+--------------------------------------------+
90 | Mode | Action |
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 |
96 | | for reading. |
97 +-------------+--------------------------------------------+
98 | ``'r|gz'`` | Open a gzip compressed *stream* for |
99 | | reading. |
100 +-------------+--------------------------------------------+
101 | ``'r|bz2'`` | Open a bzip2 compressed *stream* for |
102 | | reading. |
103 +-------------+--------------------------------------------+
104 | ``'w|'`` | Open an uncompressed *stream* for writing. |
105 +-------------+--------------------------------------------+
106 | ``'w|gz'`` | Open an gzip compressed *stream* for |
107 | | writing. |
108 +-------------+--------------------------------------------+
109 | ``'w|bz2'`` | Open an bzip2 compressed *stream* for |
110 | | writing. |
111 +-------------+--------------------------------------------+
112
113
114.. class:: TarFile
115
116 Class for reading and writing tar archives. Do not use this class directly,
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000117 better use :func:`tarfile.open` instead. See :ref:`tarfile-objects`.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000118
119
120.. function:: is_tarfile(name)
121
122 Return :const:`True` if *name* is a tar archive file, that the :mod:`tarfile`
123 module can read.
124
125
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000126.. class:: TarFileCompat(filename, mode='r', compression=TAR_PLAIN)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000127
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:
131
132
133 .. data:: TAR_PLAIN
134
135 Constant for an uncompressed tar archive.
136
137
138 .. data:: TAR_GZIPPED
139
140 Constant for a :mod:`gzip` compressed tar archive.
141
142
143.. exception:: TarError
144
145 Base class for all :mod:`tarfile` exceptions.
146
147
148.. exception:: ReadError
149
150 Is raised when a tar archive is opened, that either cannot be handled by the
151 :mod:`tarfile` module or is somehow invalid.
152
153
154.. exception:: CompressionError
155
156 Is raised when a compression method is not supported or when the data cannot be
157 decoded properly.
158
159
160.. exception:: StreamError
161
162 Is raised for the limitations that are typical for stream-like :class:`TarFile`
163 objects.
164
165
166.. exception:: ExtractError
167
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000168 Is raised for *non-fatal* errors when using :meth:`TarFile.extract`, but only if
Georg Brandl8ec7f652007-08-15 14:28:01 +0000169 :attr:`TarFile.errorlevel`\ ``== 2``.
170
171
172.. exception:: HeaderError
173
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000174 Is raised by :meth:`TarInfo.frombuf` if the buffer it gets is invalid.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000175
176 .. versionadded:: 2.6
177
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000178
Georg Brandl8ec7f652007-08-15 14:28:01 +0000179Each of the following constants defines a tar archive format that the
180:mod:`tarfile` module is able to create. See section :ref:`tar-formats` for
181details.
182
183
184.. data:: USTAR_FORMAT
185
186 POSIX.1-1988 (ustar) format.
187
188
189.. data:: GNU_FORMAT
190
191 GNU tar format.
192
193
194.. data:: PAX_FORMAT
195
196 POSIX.1-2001 (pax) format.
197
198
199.. data:: DEFAULT_FORMAT
200
201 The default format for creating archives. This is currently :const:`GNU_FORMAT`.
202
203
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000204The following variables are available on module level:
205
206
207.. data:: ENCODING
208
209 The default character encoding i.e. the value from either
210 :func:`sys.getfilesystemencoding` or :func:`sys.getdefaultencoding`.
211
212
Georg Brandl8ec7f652007-08-15 14:28:01 +0000213.. seealso::
214
215 Module :mod:`zipfile`
216 Documentation of the :mod:`zipfile` standard module.
217
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000218 `GNU tar manual, Basic Tar Format <http://www.gnu.org/software/tar/manual/html_node/Standard.html>`_
Georg Brandl8ec7f652007-08-15 14:28:01 +0000219 Documentation for tar archive files, including GNU tar extensions.
220
Georg Brandl8ec7f652007-08-15 14:28:01 +0000221
222.. _tarfile-objects:
223
224TarFile Objects
225---------------
226
227The :class:`TarFile` object provides an interface to a tar archive. A tar
228archive is a sequence of blocks. An archive member (a stored file) is made up of
229a header block followed by data blocks. It is possible to store a file in a tar
230archive several times. Each archive member is represented by a :class:`TarInfo`
231object, see :ref:`tarinfo-objects` for details.
232
233
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000234.. 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)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000235
236 All following arguments are optional and can be accessed as instance attributes
237 as well.
238
239 *name* is the pathname of the archive. It can be omitted if *fileobj* is given.
240 In this case, the file object's :attr:`name` attribute is used if it exists.
241
242 *mode* is either ``'r'`` to read from an existing archive, ``'a'`` to append
243 data to an existing file or ``'w'`` to create a new file overwriting an existing
244 one.
245
246 If *fileobj* is given, it is used for reading or writing data. If it can be
247 determined, *mode* is overridden by *fileobj*'s mode. *fileobj* will be used
248 from position 0.
249
250 .. note::
251
252 *fileobj* is not closed, when :class:`TarFile` is closed.
253
254 *format* controls the archive format. It must be one of the constants
255 :const:`USTAR_FORMAT`, :const:`GNU_FORMAT` or :const:`PAX_FORMAT` that are
256 defined at module level.
257
258 .. versionadded:: 2.6
259
260 The *tarinfo* argument can be used to replace the default :class:`TarInfo` class
261 with a different one.
262
263 .. versionadded:: 2.6
264
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000265 If *dereference* is :const:`False`, add symbolic and hard links to the archive. If it
266 is :const:`True`, add the content of the target files to the archive. This has no
Georg Brandl8ec7f652007-08-15 14:28:01 +0000267 effect on systems that do not support symbolic links.
268
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000269 If *ignore_zeros* is :const:`False`, treat an empty block as the end of the archive.
270 If it is :const:`True`, skip empty (and invalid) blocks and try to get as many members
Georg Brandl8ec7f652007-08-15 14:28:01 +0000271 as possible. This is only useful for reading concatenated or damaged archives.
272
273 *debug* can be set from ``0`` (no debug messages) up to ``3`` (all debug
274 messages). The messages are written to ``sys.stderr``.
275
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000276 If *errorlevel* is ``0``, all errors are ignored when using :meth:`TarFile.extract`.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000277 Nevertheless, they appear as error messages in the debug output, when debugging
278 is enabled. If ``1``, all *fatal* errors are raised as :exc:`OSError` or
279 :exc:`IOError` exceptions. If ``2``, all *non-fatal* errors are raised as
280 :exc:`TarError` exceptions as well.
281
282 The *encoding* and *errors* arguments control the way strings are converted to
283 unicode objects and vice versa. The default settings will work for most users.
284 See section :ref:`tar-unicode` for in-depth information.
285
286 .. versionadded:: 2.6
287
288 The *pax_headers* argument is an optional dictionary of unicode strings which
289 will be added as a pax global header if *format* is :const:`PAX_FORMAT`.
290
291 .. versionadded:: 2.6
292
293
294.. method:: TarFile.open(...)
295
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000296 Alternative constructor. The :func:`tarfile.open` function is actually a
297 shortcut to this classmethod.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000298
299
300.. method:: TarFile.getmember(name)
301
302 Return a :class:`TarInfo` object for member *name*. If *name* can not be found
303 in the archive, :exc:`KeyError` is raised.
304
305 .. note::
306
307 If a member occurs more than once in the archive, its last occurrence is assumed
308 to be the most up-to-date version.
309
310
311.. method:: TarFile.getmembers()
312
313 Return the members of the archive as a list of :class:`TarInfo` objects. The
314 list has the same order as the members in the archive.
315
316
317.. method:: TarFile.getnames()
318
319 Return the members as a list of their names. It has the same order as the list
320 returned by :meth:`getmembers`.
321
322
323.. method:: TarFile.list(verbose=True)
324
325 Print a table of contents to ``sys.stdout``. If *verbose* is :const:`False`,
326 only the names of the members are printed. If it is :const:`True`, output
327 similar to that of :program:`ls -l` is produced.
328
329
330.. method:: TarFile.next()
331
332 Return the next member of the archive as a :class:`TarInfo` object, when
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000333 :class:`TarFile` is opened for reading. Return :const:`None` if there is no more
Georg Brandl8ec7f652007-08-15 14:28:01 +0000334 available.
335
336
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000337.. method:: TarFile.extractall(path=".", members=None)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000338
339 Extract all members from the archive to the current working directory or
340 directory *path*. If optional *members* is given, it must be a subset of the
341 list returned by :meth:`getmembers`. Directory information like owner,
342 modification time and permissions are set after all members have been extracted.
343 This is done to work around two problems: A directory's modification time is
344 reset each time a file is created in it. And, if a directory's permissions do
345 not allow writing, extracting files to it will fail.
346
Lars Gustäbel89241a32007-08-30 20:24:31 +0000347 .. warning::
348
349 Never extract archives from untrusted sources without prior inspection.
350 It is possible that files are created outside of *path*, e.g. members
351 that have absolute filenames starting with ``"/"`` or filenames with two
352 dots ``".."``.
353
Georg Brandl8ec7f652007-08-15 14:28:01 +0000354 .. versionadded:: 2.5
355
356
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000357.. method:: TarFile.extract(member, path="")
Georg Brandl8ec7f652007-08-15 14:28:01 +0000358
359 Extract a member from the archive to the current working directory, using its
360 full name. Its file information is extracted as accurately as possible. *member*
361 may be a filename or a :class:`TarInfo` object. You can specify a different
362 directory using *path*.
363
364 .. note::
365
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000366 The :meth:`extract` method does not take care of several extraction issues.
367 In most cases you should consider using the :meth:`extractall` method.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000368
Lars Gustäbel89241a32007-08-30 20:24:31 +0000369 .. warning::
370
371 See the warning for :meth:`extractall`.
372
Georg Brandl8ec7f652007-08-15 14:28:01 +0000373
374.. method:: TarFile.extractfile(member)
375
376 Extract a member from the archive as a file object. *member* may be a filename
377 or a :class:`TarInfo` object. If *member* is a regular file, a file-like object
378 is returned. If *member* is a link, a file-like object is constructed from the
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000379 link's target. If *member* is none of the above, :const:`None` is returned.
Georg Brandl8ec7f652007-08-15 14:28:01 +0000380
381 .. note::
382
383 The file-like object is read-only and provides the following methods:
384 :meth:`read`, :meth:`readline`, :meth:`readlines`, :meth:`seek`, :meth:`tell`.
385
386
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000387.. method:: TarFile.add(name, arcname=None, recursive=True, exclude=None)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000388
389 Add the file *name* to the archive. *name* may be any type of file (directory,
390 fifo, symbolic link, etc.). If given, *arcname* specifies an alternative name
391 for the file in the archive. Directories are added recursively by default. This
392 can be avoided by setting *recursive* to :const:`False`. If *exclude* is given
393 it must be a function that takes one filename argument and returns a boolean
394 value. Depending on this value the respective file is either excluded
395 (:const:`True`) or added (:const:`False`).
396
397 .. versionchanged:: 2.6
398 Added the *exclude* parameter.
399
400
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000401.. method:: TarFile.addfile(tarinfo, fileobj=None)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000402
403 Add the :class:`TarInfo` object *tarinfo* to the archive. If *fileobj* is given,
404 ``tarinfo.size`` bytes are read from it and added to the archive. You can
405 create :class:`TarInfo` objects using :meth:`gettarinfo`.
406
407 .. note::
408
409 On Windows platforms, *fileobj* should always be opened with mode ``'rb'`` to
410 avoid irritation about the file size.
411
412
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000413.. method:: TarFile.gettarinfo(name=None, arcname=None, fileobj=None)
Georg Brandl8ec7f652007-08-15 14:28:01 +0000414
415 Create a :class:`TarInfo` object for either the file *name* or the file object
416 *fileobj* (using :func:`os.fstat` on its file descriptor). You can modify some
417 of the :class:`TarInfo`'s attributes before you add it using :meth:`addfile`.
418 If given, *arcname* specifies an alternative name for the file in the archive.
419
420
421.. method:: TarFile.close()
422
423 Close the :class:`TarFile`. In write mode, two finishing zero blocks are
424 appended to the archive.
425
426
427.. attribute:: TarFile.posix
428
429 Setting this to :const:`True` is equivalent to setting the :attr:`format`
430 attribute to :const:`USTAR_FORMAT`, :const:`False` is equivalent to
431 :const:`GNU_FORMAT`.
432
433 .. versionchanged:: 2.4
434 *posix* defaults to :const:`False`.
435
436 .. deprecated:: 2.6
437 Use the :attr:`format` attribute instead.
438
439
440.. attribute:: TarFile.pax_headers
441
442 A dictionary containing key-value pairs of pax global headers.
443
444 .. versionadded:: 2.6
445
Georg Brandl8ec7f652007-08-15 14:28:01 +0000446
447.. _tarinfo-objects:
448
449TarInfo Objects
450---------------
451
452A :class:`TarInfo` object represents one member in a :class:`TarFile`. Aside
453from storing all required attributes of a file (like file type, size, time,
454permissions, owner etc.), it provides some useful methods to determine its type.
455It does *not* contain the file's data itself.
456
457:class:`TarInfo` objects are returned by :class:`TarFile`'s methods
458:meth:`getmember`, :meth:`getmembers` and :meth:`gettarinfo`.
459
460
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000461.. class:: TarInfo(name="")
Georg Brandl8ec7f652007-08-15 14:28:01 +0000462
463 Create a :class:`TarInfo` object.
464
465
466.. method:: TarInfo.frombuf(buf)
467
468 Create and return a :class:`TarInfo` object from string buffer *buf*.
469
470 .. versionadded:: 2.6
471 Raises :exc:`HeaderError` if the buffer is invalid..
472
473
474.. method:: TarInfo.fromtarfile(tarfile)
475
476 Read the next member from the :class:`TarFile` object *tarfile* and return it as
477 a :class:`TarInfo` object.
478
479 .. versionadded:: 2.6
480
481
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000482.. method:: TarInfo.tobuf(format=DEFAULT_FORMAT, encoding=ENCODING, errors='strict')
Georg Brandl8ec7f652007-08-15 14:28:01 +0000483
484 Create a string buffer from a :class:`TarInfo` object. For information on the
485 arguments see the constructor of the :class:`TarFile` class.
486
487 .. versionchanged:: 2.6
488 The arguments were added.
489
490A ``TarInfo`` object has the following public data attributes:
491
492
493.. attribute:: TarInfo.name
494
495 Name of the archive member.
496
497
498.. attribute:: TarInfo.size
499
500 Size in bytes.
501
502
503.. attribute:: TarInfo.mtime
504
505 Time of last modification.
506
507
508.. attribute:: TarInfo.mode
509
510 Permission bits.
511
512
513.. attribute:: TarInfo.type
514
515 File type. *type* is usually one of these constants: :const:`REGTYPE`,
516 :const:`AREGTYPE`, :const:`LNKTYPE`, :const:`SYMTYPE`, :const:`DIRTYPE`,
517 :const:`FIFOTYPE`, :const:`CONTTYPE`, :const:`CHRTYPE`, :const:`BLKTYPE`,
518 :const:`GNUTYPE_SPARSE`. To determine the type of a :class:`TarInfo` object
519 more conveniently, use the ``is_*()`` methods below.
520
521
522.. attribute:: TarInfo.linkname
523
524 Name of the target file name, which is only present in :class:`TarInfo` objects
525 of type :const:`LNKTYPE` and :const:`SYMTYPE`.
526
527
528.. attribute:: TarInfo.uid
529
530 User ID of the user who originally stored this member.
531
532
533.. attribute:: TarInfo.gid
534
535 Group ID of the user who originally stored this member.
536
537
538.. attribute:: TarInfo.uname
539
540 User name.
541
542
543.. attribute:: TarInfo.gname
544
545 Group name.
546
547
548.. attribute:: TarInfo.pax_headers
549
550 A dictionary containing key-value pairs of an associated pax extended header.
551
552 .. versionadded:: 2.6
553
554A :class:`TarInfo` object also provides some convenient query methods:
555
556
557.. method:: TarInfo.isfile()
558
559 Return :const:`True` if the :class:`Tarinfo` object is a regular file.
560
561
562.. method:: TarInfo.isreg()
563
564 Same as :meth:`isfile`.
565
566
567.. method:: TarInfo.isdir()
568
569 Return :const:`True` if it is a directory.
570
571
572.. method:: TarInfo.issym()
573
574 Return :const:`True` if it is a symbolic link.
575
576
577.. method:: TarInfo.islnk()
578
579 Return :const:`True` if it is a hard link.
580
581
582.. method:: TarInfo.ischr()
583
584 Return :const:`True` if it is a character device.
585
586
587.. method:: TarInfo.isblk()
588
589 Return :const:`True` if it is a block device.
590
591
592.. method:: TarInfo.isfifo()
593
594 Return :const:`True` if it is a FIFO.
595
596
597.. method:: TarInfo.isdev()
598
599 Return :const:`True` if it is one of character device, block device or FIFO.
600
Georg Brandl8ec7f652007-08-15 14:28:01 +0000601
602.. _tar-examples:
603
604Examples
605--------
606
607How to extract an entire tar archive to the current working directory::
608
609 import tarfile
610 tar = tarfile.open("sample.tar.gz")
611 tar.extractall()
612 tar.close()
613
Lars Gustäbel4bfb5932008-05-17 16:50:22 +0000614How to extract a subset of a tar archive with :meth:`TarFile.extractall` using
615a generator function instead of a list::
616
617 import os
618 import tarfile
619
620 def py_files(members):
621 for tarinfo in members:
622 if os.path.splitext(tarinfo.name)[1] == ".py":
623 yield tarinfo
624
625 tar = tarfile.open("sample.tar.gz")
626 tar.extractall(members=py_files(tar))
627 tar.close()
628
Georg Brandl8ec7f652007-08-15 14:28:01 +0000629How to create an uncompressed tar archive from a list of filenames::
630
631 import tarfile
632 tar = tarfile.open("sample.tar", "w")
633 for name in ["foo", "bar", "quux"]:
634 tar.add(name)
635 tar.close()
636
637How to read a gzip compressed tar archive and display some member information::
638
639 import tarfile
640 tar = tarfile.open("sample.tar.gz", "r:gz")
641 for tarinfo in tar:
642 print tarinfo.name, "is", tarinfo.size, "bytes in size and is",
643 if tarinfo.isreg():
644 print "a regular file."
645 elif tarinfo.isdir():
646 print "a directory."
647 else:
648 print "something else."
649 tar.close()
650
Georg Brandl8ec7f652007-08-15 14:28:01 +0000651
652.. _tar-formats:
653
654Supported tar formats
655---------------------
656
657There are three tar formats that can be created with the :mod:`tarfile` module:
658
659* The POSIX.1-1988 ustar format (:const:`USTAR_FORMAT`). It supports filenames
660 up to a length of at best 256 characters and linknames up to 100 characters. The
661 maximum file size is 8 gigabytes. This is an old and limited but widely
662 supported format.
663
664* The GNU tar format (:const:`GNU_FORMAT`). It supports long filenames and
665 linknames, files bigger than 8 gigabytes and sparse files. It is the de facto
666 standard on GNU/Linux systems. :mod:`tarfile` fully supports the GNU tar
667 extensions for long names, sparse file support is read-only.
668
669* The POSIX.1-2001 pax format (:const:`PAX_FORMAT`). It is the most flexible
670 format with virtually no limits. It supports long filenames and linknames, large
671 files and stores pathnames in a portable way. However, not all tar
672 implementations today are able to handle pax archives properly.
673
674 The *pax* format is an extension to the existing *ustar* format. It uses extra
675 headers for information that cannot be stored otherwise. There are two flavours
676 of pax headers: Extended headers only affect the subsequent file header, global
677 headers are valid for the complete archive and affect all following files. All
678 the data in a pax header is encoded in *UTF-8* for portability reasons.
679
680There are some more variants of the tar format which can be read, but not
681created:
682
683* The ancient V7 format. This is the first tar format from Unix Seventh Edition,
684 storing only regular files and directories. Names must not be longer than 100
685 characters, there is no user/group name information. Some archives have
686 miscalculated header checksums in case of fields with non-ASCII characters.
687
688* The SunOS tar extended format. This format is a variant of the POSIX.1-2001
689 pax format, but is not compatible.
690
Georg Brandl8ec7f652007-08-15 14:28:01 +0000691.. _tar-unicode:
692
693Unicode issues
694--------------
695
696The tar format was originally conceived to make backups on tape drives with the
697main focus on preserving file system information. Nowadays tar archives are
698commonly used for file distribution and exchanging archives over networks. One
699problem of the original format (that all other formats are merely variants of)
700is that there is no concept of supporting different character encodings. For
701example, an ordinary tar archive created on a *UTF-8* system cannot be read
702correctly on a *Latin-1* system if it contains non-ASCII characters. Names (i.e.
703filenames, linknames, user/group names) containing these characters will appear
704damaged. Unfortunately, there is no way to autodetect the encoding of an
705archive.
706
707The pax format was designed to solve this problem. It stores non-ASCII names
708using the universal character encoding *UTF-8*. When a pax archive is read,
709these *UTF-8* names are converted to the encoding of the local file system.
710
711The details of unicode conversion are controlled by the *encoding* and *errors*
712keyword arguments of the :class:`TarFile` class.
713
714The default value for *encoding* is the local character encoding. It is deduced
715from :func:`sys.getfilesystemencoding` and :func:`sys.getdefaultencoding`. In
716read mode, *encoding* is used exclusively to convert unicode names from a pax
717archive to strings in the local character encoding. In write mode, the use of
718*encoding* depends on the chosen archive format. In case of :const:`PAX_FORMAT`,
719input names that contain non-ASCII characters need to be decoded before being
720stored as *UTF-8* strings. The other formats do not make use of *encoding*
721unless unicode objects are used as input names. These are converted to 8-bit
722character strings before they are added to the archive.
723
724The *errors* argument defines how characters are treated that cannot be
725converted to or from *encoding*. Possible values are listed in section
726:ref:`codec-base-classes`. In read mode, there is an additional scheme
727``'utf-8'`` which means that bad characters are replaced by their *UTF-8*
728representation. This is the default scheme. In write mode the default value for
729*errors* is ``'strict'`` to ensure that name information is not altered
730unnoticed.
731