mimetypes.rst 9.48 KB
Newer Older
1 2 3 4 5 6 7 8 9 10
:mod:`mimetypes` --- Map filenames to MIME types
================================================

.. module:: mimetypes
   :synopsis: Mapping of filename extensions to MIME types.
.. sectionauthor:: Fred L. Drake, Jr. <fdrake@acm.org>


.. index:: pair: MIME; content type

Raymond Hettinger's avatar
Raymond Hettinger committed
11 12 13 14
**Source code:** :source:`Lib/mimetypes.py`

--------------

15 16 17 18 19 20 21 22 23 24 25 26 27 28
The :mod:`mimetypes` module converts between a filename or URL and the MIME type
associated with the filename extension.  Conversions are provided from filename
to MIME type and from MIME type to filename extension; encodings are not
supported for the latter conversion.

The module provides one class and a number of convenience functions. The
functions are the normal interface to this module, but some applications may be
interested in the class as well.

The functions described below provide the primary interface for this module.  If
the module has not been initialized, they will call :func:`init` if they rely on
the information :func:`init` sets up.


29
.. function:: guess_type(url, strict=True)
30 31 32

   .. index:: pair: MIME; headers

33
   Guess the type of a file based on its filename or URL, given by *url*.  The
34 35 36 37 38 39
   return value is a tuple ``(type, encoding)`` where *type* is ``None`` if the
   type can't be guessed (missing or unknown suffix) or a string of the form
   ``'type/subtype'``, usable for a MIME :mailheader:`content-type` header.

   *encoding* is ``None`` for no encoding or the name of the program used to encode
   (e.g. :program:`compress` or :program:`gzip`). The encoding is suitable for use
40
   as a :mailheader:`Content-Encoding` header, **not** as a
41 42 43 44
   :mailheader:`Content-Transfer-Encoding` header. The mappings are table driven.
   Encoding suffixes are case sensitive; type suffixes are first tried case
   sensitively, then case insensitively.

45
   The optional *strict* argument is a flag specifying whether the list of known MIME types
46
   is limited to only the official types `registered with IANA
47
   <http://www.iana.org/assignments/media-types/media-types.xhtml>`_.
48 49
   When *strict* is ``True`` (the default), only the IANA types are supported; when
   *strict* is ``False``, some additional non-standard but commonly used MIME types
50 51 52
   are also recognized.


53
.. function:: guess_all_extensions(type, strict=True)
54 55 56 57 58 59 60

   Guess the extensions for a file based on its MIME type, given by *type*. The
   return value is a list of strings giving all possible filename extensions,
   including the leading dot (``'.'``).  The extensions are not guaranteed to have
   been associated with any particular data stream, but would be mapped to the MIME
   type *type* by :func:`guess_type`.

61
   The optional *strict* argument has the same meaning as with the :func:`guess_type` function.
62 63


64
.. function:: guess_extension(type, strict=True)
65 66 67 68

   Guess the extension for a file based on its MIME type, given by *type*. The
   return value is a string giving a filename extension, including the leading dot
   (``'.'``).  The extension is not guaranteed to have been associated with any
69
   particular data stream, but would be mapped to the MIME type *type* by
70 71 72
   :func:`guess_type`.  If no extension can be guessed for *type*, ``None`` is
   returned.

73
   The optional *strict* argument has the same meaning as with the :func:`guess_type` function.
74 75 76 77 78

Some additional functions and data items are available for controlling the
behavior of the module.


79
.. function:: init(files=None)
80 81 82

   Initialize the internal data structures.  If given, *files* must be a sequence
   of file names which should be used to augment the default type map.  If omitted,
83 84 85 86 87
   the file names to use are taken from :const:`knownfiles`; on Windows, the
   current registry settings are loaded.  Each file named in *files* or
   :const:`knownfiles` takes precedence over those named before it.  Calling
   :func:`init` repeatedly is allowed.

88 89 90
   Specifying an empty list for *files* will prevent the system defaults from
   being applied: only the well-known values will be present from a built-in list.

91 92
   .. versionchanged:: 3.2
      Previously, Windows registry settings were ignored.
93 94 95 96


.. function:: read_mime_types(filename)

97
   Load the type map given in the file *filename*, if it exists.  The type map is
98 99 100 101 102
   returned as a dictionary mapping filename extensions, including the leading dot
   (``'.'``), to strings of the form ``'type/subtype'``.  If the file *filename*
   does not exist or cannot be read, ``None`` is returned.


103
.. function:: add_type(type, ext, strict=True)
104

105
   Add a mapping from the MIME type *type* to the extension *ext*. When the
106 107 108
   extension is already known, the new type will replace the old one. When the type
   is already known the extension will be added to the list of known extensions.

109 110
   When *strict* is ``True`` (the default), the mapping will be added to the
   official MIME types, otherwise to the non-standard ones.
111 112 113 114 115


.. data:: inited

   Flag indicating whether or not the global data structures have been initialized.
116
   This is set to ``True`` by :func:`init`.
117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170


.. data:: knownfiles

   .. index:: single: file; mime.types

   List of type map file names commonly installed.  These files are typically named
   :file:`mime.types` and are installed in different locations by different
   packages.


.. data:: suffix_map

   Dictionary mapping suffixes to suffixes.  This is used to allow recognition of
   encoded files for which the encoding and the type are indicated by the same
   extension.  For example, the :file:`.tgz` extension is mapped to :file:`.tar.gz`
   to allow the encoding and type to be recognized separately.


.. data:: encodings_map

   Dictionary mapping filename extensions to encoding types.


.. data:: types_map

   Dictionary mapping filename extensions to MIME types.


.. data:: common_types

   Dictionary mapping filename extensions to non-standard, but commonly found MIME
   types.


An example usage of the module::

   >>> import mimetypes
   >>> mimetypes.init()
   >>> mimetypes.knownfiles
   ['/etc/mime.types', '/etc/httpd/mime.types', ... ]
   >>> mimetypes.suffix_map['.tgz']
   '.tar.gz'
   >>> mimetypes.encodings_map['.gz']
   'gzip'
   >>> mimetypes.types_map['.tgz']
   'application/x-tar-gz'


.. _mimetypes-objects:

MimeTypes Objects
-----------------

171 172
The :class:`MimeTypes` class may be useful for applications which may want more
than one MIME-type database; it provides an interface similar to the one of the
173 174 175
:mod:`mimetypes` module.


176 177 178 179 180 181 182 183 184 185 186 187 188
.. class:: MimeTypes(filenames=(), strict=True)

   This class represents a MIME-types database.  By default, it provides access to
   the same database as the rest of this module. The initial database is a copy of
   that provided by the module, and may be extended by loading additional
   :file:`mime.types`\ -style files into the database using the :meth:`read` or
   :meth:`readfp` methods.  The mapping dictionaries may also be cleared before
   loading additional data if the default data is not desired.

   The optional *filenames* parameter can be used to cause additional files to be
   loaded "on top" of the default database.


189 190 191 192 193 194
.. attribute:: MimeTypes.suffix_map

   Dictionary mapping suffixes to suffixes.  This is used to allow recognition of
   encoded files for which the encoding and the type are indicated by the same
   extension.  For example, the :file:`.tgz` extension is mapped to :file:`.tar.gz`
   to allow the encoding and type to be recognized separately.  This is initially a
195
   copy of the global :data:`suffix_map` defined in the module.
196 197 198 199 200


.. attribute:: MimeTypes.encodings_map

   Dictionary mapping filename extensions to encoding types.  This is initially a
201
   copy of the global :data:`encodings_map` defined in the module.
202 203 204 205


.. attribute:: MimeTypes.types_map

206 207 208 209
   Tuple containing two dictionaries, mapping filename extensions to MIME types:
   the first dictionary is for the non-standards types and the second one is for
   the standard types. They are initialized by :data:`common_types` and
   :data:`types_map`.
210 211


212
.. attribute:: MimeTypes.types_map_inv
213

214 215 216 217
   Tuple containing two dictionaries, mapping MIME types to a list of filename
   extensions: the first dictionary is for the non-standards types and the
   second one is for the standard types. They are initialized by
   :data:`common_types` and :data:`types_map`.
218 219


220
.. method:: MimeTypes.guess_extension(type, strict=True)
221 222 223 224 225

   Similar to the :func:`guess_extension` function, using the tables stored as part
   of the object.


226
.. method:: MimeTypes.guess_type(url, strict=True)
227 228 229 230 231

   Similar to the :func:`guess_type` function, using the tables stored as part of
   the object.


232 233 234 235 236
.. method:: MimeTypes.guess_all_extensions(type, strict=True)

   Similar to the :func:`guess_all_extensions` function, using the tables stored
   as part of the object.

237

238 239 240
.. method:: MimeTypes.read(filename, strict=True)

   Load MIME information from a file named *filename*.  This uses :meth:`readfp` to
241 242
   parse the file.

243 244 245
   If *strict* is ``True``, information will be added to list of standard types,
   else to the list of non-standard types.

246

247
.. method:: MimeTypes.readfp(fp, strict=True)
248

249
   Load MIME type information from an open file *fp*.  The file must have the format of
250 251
   the standard :file:`mime.types` files.

252 253
   If *strict* is ``True``, information will be added to the list of standard
   types, else to the list of non-standard types.
254

255 256

.. method:: MimeTypes.read_windows_registry(strict=True)
257 258 259

   Load MIME type information from the Windows registry.  Availability: Windows.

260 261 262
   If *strict* is ``True``, information will be added to the list of standard
   types, else to the list of non-standard types.

263
   .. versionadded:: 3.2