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