@@ -100,23 +100,26 @@ behavior of the module.
100100
101101.. function :: init(files=None)
102102
103- Initialize the internal data structures. If given, *files * must be a sequence
104- of file names which should be used to augment the default type map. If omitted,
105- the file names to use are taken from :const: `knownfiles `; on Windows, the
106- current registry settings are loaded. Each file named in *files * or
107- :const: `knownfiles ` takes precedence over those named before it. Calling
108- :func: `init ` repeatedly is allowed.
103+ Initialize the internal data structures. If omitted, only :const: `knownfiles ` are
104+ used to augment the default type map. If given, *files * must be a sequence of file
105+ names which are loaded after the :const: `knownfiles `.
109106
110- Specifying an empty list for *files * will prevent the system defaults from
111- being applied: only the well-known values will be present from a built-in list.
107+ The initial data structure starts with a built-in list of well-known types. On
108+ Windows, the current registry settings are loaded. Then, :const: `knownfiles ` and
109+ *files * are read in order, the latter taking precedence over the former.
112110
113111 If *files * is ``None `` the internal data structure is completely rebuilt to its
114112 initial default value. This is a stable operation and will produce the same results
115- when called multiple times.
113+ when called multiple times. If *files * is specified, each call updates the current
114+ mappings with the given files.
116115
117116 .. versionchanged :: 3.2
118117 Previously, Windows registry settings were ignored.
119118
119+ .. versionchanged :: 3.8
120+ Previously, Windows registry settings and :const: `knownfiles ` were not loaded
121+ when *files * was given.
122+
120123
121124.. function :: read_mime_types(filename)
122125
0 commit comments