Updated for hfsplus module, new gusi libs.
[python/dscho.git] / Doc / lib / libwinreg.tex
blob0f3a85af3c3b5182bfca96ae4a1866c384cde744
1 \section{\module{_winreg} --
2 Windows registry access}
4 \declaremodule[-winreg]{extension}{_winreg}
5 \platform{Windows}
6 \modulesynopsis{Routines and objects for manipulating the Windows registry.}
7 \sectionauthor{Mark Hammond}{MarkH@ActiveState.com}
9 \versionadded{2.0}
11 These functions expose the Windows registry API to Python. Instead of
12 using an integer as the registry handle, a handle object is used to
13 ensure that the handles are closed correctly, even if the programmer
14 neglects to explicitly close them.
16 This module exposes a very low-level interface to the Windows
17 registry; it is expected that in the future a new \code{winreg}
18 module will be created offering a higher-level interface to the
19 registry API.
21 This module offers the following functions:
24 \begin{funcdesc}{CloseKey}{hkey}
25 Closes a previously opened registry key.
26 The hkey argument specifies a previously opened key.
28 Note that if \var{hkey} is not closed using this method, (or the
29 \method{handle.Close()} closed when the \var{hkey} object is
30 destroyed by Python.
31 \end{funcdesc}
34 \begin{funcdesc}{ConnectRegistry}{computer_name, key}
35 Establishes a connection to a predefined registry handle on
36 another computer, and returns a \dfn{handle object}
38 \var{computer_name} is the name of the remote computer, of the
39 form \samp{\e\e computername}. If \code{None}, the local computer
40 is used.
42 \var{key} is the predefined handle to connect to.
44 The return value is the handle of the opened key.
45 If the function fails, an \exception{EnvironmentError} exception is
46 raised.
47 \end{funcdesc}
50 \begin{funcdesc}{CreateKey}{key, sub_key}
51 Creates or opens the specified key, returning a \dfn{handle object}
53 \var{key} is an already open key, or one of the predefined
54 \constant{HKEY_*} constants.
56 \var{sub_key} is a string that names the key this method opens
57 or creates.
59 If \var{key} is one of the predefined keys, \var{sub_key} may
60 be \code{None}. In that case, the handle returned is the same key handle
61 passed in to the function.
63 If the key already exists, this function opens the existing key
65 The return value is the handle of the opened key.
66 If the function fails, an \exception{EnvironmentError} exception is
67 raised.
68 \end{funcdesc}
70 \begin{funcdesc}{DeleteKey}{key, sub_key}
71 Deletes the specified key.
73 \var{key} is an already open key, or any one of the predefined
74 \constant{HKEY_*} constants.
76 \var{sub_key} is a string that must be a subkey of the key
77 identified by the \var{key} parameter. This value must not be
78 \code{None}, and the key may not have subkeys.
80 \emph{This method can not delete keys with subkeys.}
82 If the method succeeds, the entire key, including all of its values,
83 is removed. If the method fails, an \exception{EnvironmentError}
84 exception is raised.
85 \end{funcdesc}
88 \begin{funcdesc}{DeleteValue}{key, value}
89 Removes a named value from a registry key.
91 \var{key} is an already open key, or one of the predefined
92 \constant{HKEY_*} constants.
94 \var{value} is a string that identifies the value to remove.
95 \end{funcdesc}
98 \begin{funcdesc}{EnumKey}{key, index}
99 Enumerates subkeys of an open registry key, returning a string.
101 \var{key} is an already open key, or any one of the predefined
102 \constant{HKEY_*} constants.
104 \var{index} is an integer that identifies the index of the key to
105 retrieve.
107 The function retrieves the name of one subkey each time it
108 is called. It is typically called repeatedly until an
109 \exception{EnvironmentError} exception
110 is raised, indicating, no more values are available.
111 \end{funcdesc}
114 \begin{funcdesc}{EnumValue}{key, index}
115 Enumerates values of an open registry key, returning a tuple.
117 \var{key} is an already open key, or any one of the predefined
118 \constant{HKEY_*} constants.
120 \var{index} is an integer that identifies the index of the value
121 to retrieve.
123 The function retrieves the name of one subkey each time it is
124 called. It is typically called repeatedly, until an
125 \exception{EnvironmentError} exception is raised, indicating
126 no more values.
128 The result is a tuple of 3 items:
130 \begin{tableii}{c|p{3in}}{code}{Index}{Meaning}
131 \lineii{0}{A string that identifies the value name}
132 \lineii{1}{An object that holds the value data, and whose
133 type depends on the underlying registry type}
134 \lineii{2}{An integer that identifies the type of the value data}
135 \end{tableii}
137 \end{funcdesc}
140 \begin{funcdesc}{FlushKey}{key}
141 Writes all the attributes of a key to the registry.
143 \var{key} is an already open key, or one of the predefined
144 \constant{HKEY_*} constants.
146 It is not necessary to call RegFlushKey to change a key.
147 Registry changes are flushed to disk by the registry using its lazy
148 flusher. Registry changes are also flushed to disk at system
149 shutdown. Unlike \function{CloseKey()}, the \function{FlushKey()} method
150 returns only when all the data has been written to the registry.
151 An application should only call \function{FlushKey()} if it requires absolute
152 certainty that registry changes are on disk.
154 \emph{If you don't know whether a \function{FlushKey()} call is required, it
155 probably isn't.}
157 \end{funcdesc}
160 \begin{funcdesc}{RegLoadKey}{key, sub_key, file_name}
161 Creates a subkey under the specified key and stores registration
162 information from a specified file into that subkey.
164 \var{key} is an already open key, or any of the predefined
165 \constant{HKEY_*} constants.
167 \var{sub_key} is a string that identifies the sub_key to load
169 \var {file_name} is the name of the file to load registry data from.
170 This file must have been created with the \function{SaveKey()} function.
171 Under the file allocation table (FAT) file system, the filename may not
172 have an extension.
174 A call to LoadKey() fails if the calling process does not have the
175 \constant{SE_RESTORE_PRIVILEGE} privilege. Note that privileges
176 are different than permissions - see the Win32 documentation for
177 more details.
179 If \var{key} is a handle returned by \function{ConnectRegistry()},
180 then the path specified in \var{fileName} is relative to the
181 remote computer.
183 The Win32 documentation implies \var{key} must be in the
184 \constant{HKEY_USER} or \constant{HKEY_LOCAL_MACHINE} tree.
185 This may or may not be true.
186 \end{funcdesc}
189 \begin{funcdesc}{OpenKey}{key, sub_key\optional{, res\code{ = 0}}\optional{, sam\code{ = \constant{KEY_READ}}}}
190 Opens the specified key, returning a \dfn{handle object}
192 \var{key} is an already open key, or any one of the predefined
193 \constant{HKEY_*} constants.
195 \var{sub_key} is a string that identifies the sub_key to open
197 \var{res} is a reserved integer, and must be zero. The default is zero.
199 \var{sam} is an integer that specifies an access mask that describes
200 the desired security access for the key. Default is \constant{KEY_READ}
202 The result is a new handle to the specified key
204 If the function fails, \exception{EnvironmentError} is raised.
205 \end{funcdesc}
208 \begin{funcdesc}{OpenKeyEx}{}
209 The functionality of \function{OpenKeyEx()} is provided via
210 \function{OpenKey()}, by the use of default arguments.
211 \end{funcdesc}
214 \begin{funcdesc}{QueryInfoKey}{key}
215 Returns information about a key, as a tuple.
217 \var{key} is an already open key, or one of the predefined
218 \constant{HKEY_*} constants.
220 The result is a tuple of 3 items:
222 \begin{tableii}{c|p{3in}}{code}{Index}{Meaning}
223 \lineii{0}{An integer giving the number of sub keys this key has.}
224 \lineii{1}{An integer giving the number of values this key has.}
225 \lineii{2}{A long integer giving when the key was last modified (if
226 available) as 100's of nanoseconds since Jan 1, 1600.}
227 \end{tableii}
228 \end{funcdesc}
231 \begin{funcdesc}{QueryValue}{key, sub_key}
232 Retrieves the unnamed value for a key, as a string
234 \var{key} is an already open key, or one of the predefined
235 \constant{HKEY_*} constants.
237 \var{sub_key} is a string that holds the name of the subkey with which
238 the value is associated. If this parameter is \code{None} or empty, the
239 function retrieves the value set by the \function{SetValue()} method
240 for the key identified by \var{key}.
242 Values in the registry have name, type, and data components. This
243 method retrieves the data for a key's first value that has a NULL name.
244 But the underlying API call doesn't return the type, Lame Lame Lame,
245 DO NOT USE THIS!!!
246 \end{funcdesc}
249 \begin{funcdesc}{QueryValueEx}{key, value_name}
250 Retrieves the type and data for a specified value name associated with
251 an open registry key.
253 \var{key} is an already open key, or one of the predefined
254 \constant{HKEY_*} constants.
256 \var{value_name} is a string indicating the value to query.
258 The result is a tuple of 2 items:
260 \begin{tableii}{c|p{3in}}{code}{Index}{Meaning}
261 \lineii{0}{The value of the registry item.}
262 \lineii{1}{An integer giving the registry type for this value.}
263 \end{tableii}
264 \end{funcdesc}
267 \begin{funcdesc}{SaveKey}{key, file_name}
268 Saves the specified key, and all its subkeys to the specified file.
270 \var{key} is an already open key, or one of the predefined
271 \constant{HKEY_*} constants.
273 \var{file_name} is the name of the file to save registry data to.
274 This file cannot already exist. If this filename includes an extension,
275 it cannot be used on file allocation table (FAT) file systems by the
276 \method{LoadKey()}, \method{ReplaceKey()} or
277 \method{RestoreKey()} methods.
279 If \var{key} represents a key on a remote computer, the path
280 described by \var{file_name} is relative to the remote computer.
281 The caller of this method must possess the \constant{SeBackupPrivilege}
282 security privilege. Note that privileges are different than permissions
283 - see the Win32 documentation for more details.
285 This function passes NULL for \var{security_attributes} to the API.
286 \end{funcdesc}
289 \begin{funcdesc}{SetValue}{key, sub_key, type, value}
290 Associates a value with a specified key.
292 \var{key} is an already open key, or one of the predefined
293 \constant{HKEY_*} constants.
295 \var{sub_key} is a string that names the subkey with which the value
296 is associated.
298 \var{type} is an integer that specifies the type of the data.
299 Currently this must be \constant{REG_SZ}, meaning only strings are
300 supported. Use the \function{SetValueEx()} function for support for
301 other data types.
303 \var{value} is a string that specifies the new value.
305 If the key specified by the \var{sub_key} parameter does not exist,
306 the SetValue function creates it.
308 Value lengths are limited by available memory. Long values (more than
309 2048 bytes) should be stored as files with the filenames stored in
310 the configuration registry. This helps the registry perform
311 efficiently.
313 The key identified by the \var{key} parameter must have been
314 opened with \constant{KEY_SET_VALUE} access.
315 \end{funcdesc}
318 \begin{funcdesc}{SetValueEx}{key, value_name, reserved, type, value}
319 Stores data in the value field of an open registry key.
321 \var{key} is an already open key, or one of the predefined
322 \constant{HKEY_*} constants.
324 \var{sub_key} is a string that names the subkey with which the
325 value is associated.
327 \var{type} is an integer that specifies the type of the data.
328 This should be one of the following constants defined in this module:
330 \begin{tableii}{l|p{3in}}{constant}{Constant}{Meaning}
331 \lineii{REG_BINARY}{Binary data in any form.}
332 \lineii{REG_DWORD}{A 32-bit number.}
333 \lineii{REG_DWORD_LITTLE_ENDIAN}{A 32-bit number in little-endian format.}
334 \lineii{REG_DWORD_BIG_ENDIAN}{A 32-bit number in big-endian format.}
335 \lineii{REG_EXPAND_SZ}{Null-terminated string containing references
336 to environment variables (\samp{\%PATH\%}).}
337 \lineii{REG_LINK}{A Unicode symbolic link.}
338 \lineii{REG_MULTI_SZ}{A sequence of null-terminated strings,
339 terminated by two null characters. (Python handles
340 this termination automatically.)}
341 \lineii{REG_NONE}{No defined value type.}
342 \lineii{REG_RESOURCE_LIST}{A device-driver resource list.}
343 \lineii{REG_SZ}{A null-terminated string.}
344 \end{tableii}
346 \var{reserved} can be anything - zero is always passed to the
347 API.
349 \var{value} is a string that specifies the new value.
351 This method can also set additional value and type information for the
352 specified key. The key identified by the key parameter must have been
353 opened with \constant{KEY_SET_VALUE} access.
355 To open the key, use the \function{CreateKeyEx()} or
356 \function{OpenKey()} methods.
358 Value lengths are limited by available memory. Long values (more than
359 2048 bytes) should be stored as files with the filenames stored in
360 the configuration registry. This helps the registry perform efficiently.
361 \end{funcdesc}
365 \subsection{Registry Handle Objects \label{handle-object}}
367 This object wraps a Windows HKEY object, automatically closing it when
368 the object is destroyed. To guarantee cleanup, you can call either
369 the \method{Close()} method on the object, or the
370 \function{CloseKey()} function.
372 All registry functions in this module return one of these objects.
374 All registry functions in this module which accept a handle object
375 also accept an integer, however, use of the handle object is
376 encouraged.
378 Handle objects provide semantics for \method{__nonzero__()} - thus
379 \begin{verbatim}
380 if handle:
381 print "Yes"
382 \end{verbatim}
383 will print \code{Yes} if the handle is currently valid (has not been
384 closed or detached).
386 The object also support comparison semantics, so handle
387 objects will compare true if they both reference the same
388 underlying Windows handle value.
390 Handle objects can be converted to an integer (eg, using the
391 builtin \function{int()} function, in which case the underlying
392 Windows handle value is returned. You can also use the
393 \method{Detach()} method to return the integer handle, and
394 also disconnect the Windows handle from the handle object.
396 \begin{methoddesc}{Close}{}
397 Closes the underlying Windows handle.
399 If the handle is already closed, no error is raised.
400 \end{methoddesc}
403 \begin{methoddesc}{Detach}{}
404 Detaches the Windows handle from the handle object.
406 The result is an integer (or long on 64 bit Windows) that holds
407 the value of the handle before it is detached. If the
408 handle is already detached or closed, this will return zero.
410 After calling this function, the handle is effectively invalidated,
411 but the handle is not closed. You would call this function when
412 you need the underlying Win32 handle to exist beyond the lifetime
413 of the handle object.
414 \end{methoddesc}