| 
									
										
										
										
											1998-08-10 19:42:37 +00:00
										 |  |  | \section{Built-in Functions \label{built-in-funcs}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | The Python interpreter has a number of functions built into it that | 
					
						
							|  |  |  | are always available.  They are listed here in alphabetical order. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \setindexsubitem{(built-in function)} | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{__import__}{name\optional{, globals\optional{, locals\optional{, fromlist}}}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   This function is invoked by the \keyword{import}\stindex{import} | 
					
						
							|  |  |  |   statement.  It mainly exists so that you can replace it with another | 
					
						
							|  |  |  |   function that has a compatible interface, in order to change the | 
					
						
							|  |  |  |   semantics of the \keyword{import} statement.  For examples of why | 
					
						
							|  |  |  |   and how you would do this, see the standard library modules | 
					
						
							|  |  |  |   \module{ihooks}\refstmodindex{ihooks} and | 
					
						
							|  |  |  |   \refmodule{rexec}\refstmodindex{rexec}.  See also the built-in | 
					
						
							|  |  |  |   module \refmodule{imp}\refbimodindex{imp}, which defines some useful | 
					
						
							|  |  |  |   operations out of which you can build your own | 
					
						
							|  |  |  |   \function{__import__()} function. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   For example, the statement \samp{import spam} results in the | 
					
						
							|  |  |  |   following call: \code{__import__('spam',} \code{globals(),} | 
					
						
							|  |  |  |   \code{locals(), [])}; the statement \samp{from spam.ham import eggs} | 
					
						
							|  |  |  |   results in \samp{__import__('spam.ham', globals(), locals(), | 
					
						
							|  |  |  |   ['eggs'])}.  Note that even though \code{locals()} and | 
					
						
							|  |  |  |   \code{['eggs']} are passed in as arguments, the | 
					
						
							|  |  |  |   \function{__import__()} function does not set the local variable | 
					
						
							|  |  |  |   named \code{eggs}; this is done by subsequent code that is generated | 
					
						
							|  |  |  |   for the import statement.  (In fact, the standard implementation | 
					
						
							|  |  |  |   does not use its \var{locals} argument at all, and uses its | 
					
						
							|  |  |  |   \var{globals} only to determine the package context of the | 
					
						
							|  |  |  |   \keyword{import} statement.) | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   When the \var{name} variable is of the form \code{package.module}, | 
					
						
							|  |  |  |   normally, the top-level package (the name up till the first dot) is | 
					
						
							|  |  |  |   returned, \emph{not} the module named by \var{name}.  However, when | 
					
						
							|  |  |  |   a non-empty \var{fromlist} argument is given, the module named by | 
					
						
							|  |  |  |   \var{name} is returned.  This is done for compatibility with the | 
					
						
							|  |  |  |   bytecode generated for the different kinds of import statement; when | 
					
						
							| 
									
										
										
										
											2002-10-22 20:31:22 +00:00
										 |  |  |   using \samp{import spam.ham.eggs}, the top-level package \module{spam} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   must be placed in the importing namespace, but when using \samp{from | 
					
						
							|  |  |  |   spam.ham import eggs}, the \code{spam.ham} subpackage must be used | 
					
						
							|  |  |  |   to find the \code{eggs} variable.  As a workaround for this | 
					
						
							|  |  |  |   behavior, use \function{getattr()} to extract the desired | 
					
						
							|  |  |  |   components.  For example, you could define the following helper: | 
					
						
							| 
									
										
										
										
											1998-12-04 15:32:17 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | \begin{verbatim} | 
					
						
							|  |  |  | def my_import(name): | 
					
						
							|  |  |  |     mod = __import__(name) | 
					
						
							| 
									
										
										
										
											2002-10-22 20:31:22 +00:00
										 |  |  |     components = name.split('.') | 
					
						
							| 
									
										
										
										
											1998-12-04 15:32:17 +00:00
										 |  |  |     for comp in components[1:]: | 
					
						
							|  |  |  |         mod = getattr(mod, comp) | 
					
						
							|  |  |  |     return mod | 
					
						
							|  |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{abs}{x} | 
					
						
							|  |  |  |   Return the absolute value of a number.  The argument may be a plain | 
					
						
							| 
									
										
										
										
											1997-06-02 17:21:20 +00:00
										 |  |  |   or long integer or a floating point number.  If the argument is a | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  |   complex number, its magnitude is returned. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{apply}{function, args\optional{, keywords}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   The \var{function} argument must be a callable object (a | 
					
						
							|  |  |  |   user-defined or built-in function or method, or a class object) and | 
					
						
							| 
									
										
										
										
											2001-11-07 06:22:25 +00:00
										 |  |  |   the \var{args} argument must be a sequence.  The \var{function} is | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   called with \var{args} as the argument list; the number of arguments | 
					
						
							| 
									
										
										
										
											2002-09-04 23:52:42 +00:00
										 |  |  |   is the length of the tuple. | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   If the optional \var{keywords} argument is present, it must be a | 
					
						
							|  |  |  |   dictionary whose keys are strings.  It specifies keyword arguments | 
					
						
							|  |  |  |   to be added to the end of the the argument list. | 
					
						
							| 
									
										
										
										
											2001-11-07 06:22:25 +00:00
										 |  |  |   Calling \function{apply()} is different from just calling | 
					
						
							| 
									
										
										
										
											2001-11-07 06:28:47 +00:00
										 |  |  |   \code{\var{function}(\var{args})}, since in that case there is always | 
					
						
							| 
									
										
										
										
											2001-11-07 06:22:25 +00:00
										 |  |  |   exactly one argument.  The use of \function{apply()} is equivalent | 
					
						
							|  |  |  |   to \code{\var{function}(*\var{args}, **\var{keywords})}. | 
					
						
							| 
									
										
										
										
											2002-08-22 14:27:35 +00:00
										 |  |  |   Use of \function{apply()} is not necessary since the ``extended call | 
					
						
							|  |  |  |   syntax,'' as used in the last example, is completely equivalent. | 
					
						
							| 
									
										
										
										
											2003-01-02 04:54:04 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \deprecated{2.3}{Use the extended call syntax instead, as described | 
					
						
							|  |  |  |                    above.} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{bool}{\optional{x}} | 
					
						
							| 
									
										
										
										
											2002-04-03 22:41:51 +00:00
										 |  |  |   Convert a value to a Boolean, using the standard truth testing | 
					
						
							|  |  |  |   procedure.  If \code{x} is false, this returns \code{False}; | 
					
						
							|  |  |  |   otherwise it returns \code{True}.  \code{bool} is also a class, | 
					
						
							|  |  |  |   which is a subclass of \code{int}.  Class \code{bool} cannot be | 
					
						
							|  |  |  |   subclassed further.  Its only instances are \code{False} and | 
					
						
							| 
									
										
										
										
											2003-06-11 09:15:26 +00:00
										 |  |  |   \code{True}. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-04-03 22:41:51 +00:00
										 |  |  | \indexii{Boolean}{type} | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | \versionadded{2.2.1} | 
					
						
							| 
									
										
										
										
											2003-06-11 09:15:26 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-17 02:37:06 +00:00
										 |  |  |   \versionchanged[If no argument is given, this function returns  | 
					
						
							|  |  |  |                   \code{False}]{2.3} | 
					
						
							| 
									
										
										
										
											2002-04-03 22:41:51 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1999-03-19 19:10:14 +00:00
										 |  |  | \begin{funcdesc}{buffer}{object\optional{, offset\optional{, size}}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   The \var{object} argument must be an object that supports the buffer | 
					
						
							|  |  |  |   call interface (such as strings, arrays, and buffers).  A new buffer | 
					
						
							|  |  |  |   object will be created which references the \var{object} argument. | 
					
						
							|  |  |  |   The buffer object will be a slice from the beginning of \var{object} | 
					
						
							|  |  |  |   (or from the specified \var{offset}). The slice will extend to the | 
					
						
							|  |  |  |   end of \var{object} (or will have a length given by the \var{size} | 
					
						
							|  |  |  |   argument). | 
					
						
							| 
									
										
										
										
											1999-03-19 19:10:14 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \begin{funcdesc}{callable}{object} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return true if the \var{object} argument appears callable, false if | 
					
						
							|  |  |  |   not.  If this returns true, it is still possible that a call fails, | 
					
						
							|  |  |  |   but if it is false, calling \var{object} will never succeed.  Note | 
					
						
							|  |  |  |   that classes are callable (calling a class returns a new instance); | 
					
						
							|  |  |  |   class instances are callable if they have a \method{__call__()} | 
					
						
							|  |  |  |   method. | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{chr}{i} | 
					
						
							|  |  |  |   Return a string of one character whose \ASCII{} code is the integer | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   \var{i}.  For example, \code{chr(97)} returns the string \code{'a'}. | 
					
						
							|  |  |  |   This is the inverse of \function{ord()}.  The argument must be in | 
					
						
							|  |  |  |   the range [0..255], inclusive; \exception{ValueError} will be raised | 
					
						
							|  |  |  |   if \var{i} is outside that range. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | \begin{funcdesc}{classmethod}{function} | 
					
						
							|  |  |  |   Return a class method for \var{function}. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   A class method receives the class as implicit first argument, | 
					
						
							|  |  |  |   just like an instance method receives the instance. | 
					
						
							|  |  |  |   To declare a class method, use this idiom: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{verbatim} | 
					
						
							|  |  |  | class C: | 
					
						
							|  |  |  |     def f(cls, arg1, arg2, ...): ... | 
					
						
							|  |  |  |     f = classmethod(f) | 
					
						
							|  |  |  | \end{verbatim} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   It can be called either on the class (such as \code{C.f()}) or on an | 
					
						
							|  |  |  |   instance (such as \code{C().f()}).  The instance is ignored except for | 
					
						
							|  |  |  |   its class. | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  |   If a class method is called for a derived class, the derived class | 
					
						
							|  |  |  |   object is passed as the implied first argument. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-07-02 12:27:43 +00:00
										 |  |  |   Class methods are different than \Cpp{} or Java static methods. | 
					
						
							| 
									
										
										
										
											2003-06-26 03:11:57 +00:00
										 |  |  |   If you want those, see \function{staticmethod()} in this section. | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  |   \versionadded{2.2} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{cmp}{x, y} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Compare the two objects \var{x} and \var{y} and return an integer | 
					
						
							|  |  |  |   according to the outcome.  The return value is negative if \code{\var{x} | 
					
						
							|  |  |  |   < \var{y}}, zero if \code{\var{x} == \var{y}} and strictly positive if | 
					
						
							|  |  |  |   \code{\var{x} > \var{y}}. | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{coerce}{x, y} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Return a tuple consisting of the two numeric arguments converted to | 
					
						
							|  |  |  |   a common type, using the same rules as used by arithmetic | 
					
						
							|  |  |  |   operations. | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-09-03 08:35:41 +00:00
										 |  |  | \begin{funcdesc}{compile}{string, filename, kind\optional{, | 
					
						
							| 
									
										
										
										
											2001-08-27 20:02:17 +00:00
										 |  |  |                           flags\optional{, dont_inherit}}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Compile the \var{string} into a code object.  Code objects can be | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   executed by an \keyword{exec} statement or evaluated by a call to | 
					
						
							|  |  |  |   \function{eval()}.  The \var{filename} argument should | 
					
						
							| 
									
										
										
										
											2001-09-29 14:28:52 +00:00
										 |  |  |   give the file from which the code was read; pass some recognizable value | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   if it wasn't read from a file (\code{'<string>'} is commonly used). | 
					
						
							|  |  |  |   The \var{kind} argument specifies what kind of code must be | 
					
						
							|  |  |  |   compiled; it can be \code{'exec'} if \var{string} consists of a | 
					
						
							|  |  |  |   sequence of statements, \code{'eval'} if it consists of a single | 
					
						
							|  |  |  |   expression, or \code{'single'} if it consists of a single | 
					
						
							|  |  |  |   interactive statement (in the latter case, expression statements | 
					
						
							|  |  |  |   that evaluate to something else than \code{None} will printed). | 
					
						
							| 
									
										
										
										
											2001-08-27 20:02:17 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-09-29 14:28:52 +00:00
										 |  |  |   When compiling multi-line statements, two caveats apply: line | 
					
						
							|  |  |  |   endings must be represented by a single newline character | 
					
						
							|  |  |  |   (\code{'\e n'}), and the input must be terminated by at least one | 
					
						
							|  |  |  |   newline character.  If line endings are represented by | 
					
						
							|  |  |  |   \code{'\e r\e n'}, use the string \method{replace()} method to | 
					
						
							|  |  |  |   change them into \code{'\e n'}. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   The optional arguments \var{flags} and \var{dont_inherit} | 
					
						
							| 
									
										
										
										
											2001-08-27 20:02:17 +00:00
										 |  |  |   (which are new in Python 2.2) control which future statements (see | 
					
						
							|  |  |  |   \pep{236}) affect the compilation of \var{string}.  If neither is | 
					
						
							|  |  |  |   present (or both are zero) the code is compiled with those future | 
					
						
							|  |  |  |   statements that are in effect in the code that is calling compile. | 
					
						
							|  |  |  |   If the \var{flags} argument is given and \var{dont_inherit} is not | 
					
						
							|  |  |  |   (or is zero) then the future statements specified by the \var{flags} | 
					
						
							|  |  |  |   argument are used in addition to those that would be used anyway. | 
					
						
							|  |  |  |   If \var{dont_inherit} is a non-zero integer then the \var{flags} | 
					
						
							|  |  |  |   argument is it -- the future statements in effect around the call to | 
					
						
							|  |  |  |   compile are ignored. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   Future statemants are specified by bits which can be bitwise or-ed | 
					
						
							|  |  |  |   together to specify multiple statements.  The bitfield required to | 
					
						
							|  |  |  |   specify a given feature can be found as the \member{compiler_flag} | 
					
						
							|  |  |  |   attribute on the \class{_Feature} instance in the | 
					
						
							|  |  |  |   \module{__future__} module. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{complex}{\optional{real\optional{, imag}}} | 
					
						
							| 
									
										
										
										
											1999-03-25 21:23:26 +00:00
										 |  |  |   Create a complex number with the value \var{real} + \var{imag}*j or | 
					
						
							| 
									
										
										
										
											2001-12-13 19:52:22 +00:00
										 |  |  |   convert a string or number to a complex number.  If the first | 
					
						
							|  |  |  |   parameter is a string, it will be interpreted as a complex number | 
					
						
							|  |  |  |   and the function must be called without a second parameter.  The | 
					
						
							|  |  |  |   second parameter can never be a string. | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   Each argument may be any numeric type (including complex). | 
					
						
							|  |  |  |   If \var{imag} is omitted, it defaults to zero and the function | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   serves as a numeric conversion function like \function{int()}, | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   \function{long()} and \function{float()}.  If both arguments | 
					
						
							|  |  |  |   are omitted, returns \code{0j}. | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{delattr}{object, name} | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   This is a relative of \function{setattr()}.  The arguments are an | 
					
						
							| 
									
										
										
										
											1994-08-16 22:15:11 +00:00
										 |  |  |   object and a string.  The string must be the name | 
					
						
							|  |  |  |   of one of the object's attributes.  The function deletes | 
					
						
							|  |  |  |   the named attribute, provided the object allows it.  For example, | 
					
						
							| 
									
										
										
										
											1995-03-07 10:14:09 +00:00
										 |  |  |   \code{delattr(\var{x}, '\var{foobar}')} is equivalent to | 
					
						
							| 
									
										
										
										
											1994-08-16 22:15:11 +00:00
										 |  |  |   \code{del \var{x}.\var{foobar}}. | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-29 22:25:45 +00:00
										 |  |  | \begin{funcdesc}{dict}{\optional{mapping-or-sequence}} | 
					
						
							| 
									
										
										
										
											2002-11-23 09:45:04 +00:00
										 |  |  |   Return a new dictionary initialized from an optional positional | 
					
						
							|  |  |  |   argument or from a set of keyword arguments. | 
					
						
							|  |  |  |   If no arguments are given, return a new empty dictionary. | 
					
						
							|  |  |  |   If the positional argument is a mapping object, return a dictionary | 
					
						
							|  |  |  |   mapping the same keys to the same values as does the mapping object. | 
					
						
							|  |  |  |   Otherwise the positional argument must be a sequence, a container that | 
					
						
							|  |  |  |   supports iteration, or an iterator object.  The elements of the argument | 
					
						
							|  |  |  |   must each also be of one of those kinds, and each must in turn contain | 
					
						
							| 
									
										
											  
											
												Generalize dictionary() to accept a sequence of 2-sequences.  At the
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2.  These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object.  For now, I left these
functions file static, so no corresponding doc changes.  It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x".  Got a better name?  "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex:  Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
  iteration, or an iterator object" is getting to be a PITA.  Many
  months ago I suggested factoring this out into "iterable object",
  where the definition of that could include being explicit about
  generators too (as is, I'm not sure a reader outside of PythonLabs
  could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple():  When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
											
										 
											2001-10-26 05:06:50 +00:00
										 |  |  |   exactly two objects.  The first is used as a key in the new dictionary, | 
					
						
							|  |  |  |   and the second as the key's value.  If a given key is seen more than | 
					
						
							|  |  |  |   once, the last value associated with it is retained in the new | 
					
						
							|  |  |  |   dictionary. | 
					
						
							| 
									
										
										
										
											2002-11-23 09:45:04 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   If keyword arguments are given, the keywords themselves with their | 
					
						
							|  |  |  |   associated values are added as items to the dictionary. If a key | 
					
						
							|  |  |  |   is specified both in the positional argument and as a keyword argument, | 
					
						
							|  |  |  |   the value associated with the keyword is retained in the dictionary. | 
					
						
							| 
									
										
											  
											
												Generalize dictionary() to accept a sequence of 2-sequences.  At the
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2.  These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object.  For now, I left these
functions file static, so no corresponding doc changes.  It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x".  Got a better name?  "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex:  Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
  iteration, or an iterator object" is getting to be a PITA.  Many
  months ago I suggested factoring this out into "iterable object",
  where the definition of that could include being explicit about
  generators too (as is, I'm not sure a reader outside of PythonLabs
  could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple():  When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
											
										 
											2001-10-26 05:06:50 +00:00
										 |  |  |   For example, these all return a dictionary equal to | 
					
						
							| 
									
										
										
										
											2002-11-23 09:45:04 +00:00
										 |  |  |   \code{\{"one": 2, "two": 3\}}: | 
					
						
							| 
									
										
										
										
											2001-10-26 15:04:33 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \begin{itemize} | 
					
						
							| 
									
										
										
										
											2002-11-23 09:45:04 +00:00
										 |  |  |     \item \code{dict(\{'one': 2, 'two': 3\})} | 
					
						
							|  |  |  |     \item \code{dict(\{'one': 2, 'two': 3\}.items())} | 
					
						
							|  |  |  |     \item \code{dict(\{'one': 2, 'two': 3\}.iteritems())} | 
					
						
							|  |  |  |     \item \code{dict(zip(('one', 'two'), (2, 3)))} | 
					
						
							|  |  |  |     \item \code{dict([['two', 3], ['one', 2]])} | 
					
						
							|  |  |  |     \item \code{dict(one=2, two=3)} | 
					
						
							|  |  |  |     \item \code{dict([(['one', 'two'][i-2], i) for i in (2, 3)])} | 
					
						
							| 
									
										
										
										
											2001-10-26 15:04:33 +00:00
										 |  |  |   \end{itemize} | 
					
						
							| 
									
										
										
										
											2002-03-06 02:29:30 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \versionadded{2.2} | 
					
						
							| 
									
										
										
										
											2002-11-23 15:02:13 +00:00
										 |  |  |   \versionchanged[Support for building a dictionary from keyword | 
					
						
							|  |  |  |                   arguments added]{2.3} | 
					
						
							| 
									
										
											  
											
												Generalize dictionary() to accept a sequence of 2-sequences.  At the
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2.  These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object.  For now, I left these
functions file static, so no corresponding doc changes.  It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x".  Got a better name?  "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex:  Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
  iteration, or an iterator object" is getting to be a PITA.  Many
  months ago I suggested factoring this out into "iterable object",
  where the definition of that could include being explicit about
  generators too (as is, I'm not sure a reader outside of PythonLabs
  could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple():  When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
											
										 
											2001-10-26 05:06:50 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-04-16 22:10:27 +00:00
										 |  |  | \begin{funcdesc}{dir}{\optional{object}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Without arguments, return the list of names in the current local | 
					
						
							| 
									
										
										
										
											1997-12-30 20:38:16 +00:00
										 |  |  |   symbol table.  With an argument, attempts to return a list of valid | 
					
						
							| 
									
										
										
										
											2002-02-23 04:40:15 +00:00
										 |  |  |   attributes for that object.  This information is gleaned from the | 
					
						
							| 
									
										
										
										
											2001-12-03 17:32:27 +00:00
										 |  |  |   object's \member{__dict__} attribute, if defined, and from the class | 
					
						
							| 
									
										
										
										
											2002-02-23 04:40:15 +00:00
										 |  |  |   or type object.  The list is not necessarily complete. | 
					
						
							|  |  |  |   If the object is a module object, the list contains the names of the | 
					
						
							|  |  |  |   module's attributes. | 
					
						
							|  |  |  |   If the object is a type or class object, | 
					
						
							|  |  |  |   the list contains the names of its attributes, | 
					
						
							|  |  |  |   and recursively of the attributes of its bases. | 
					
						
							|  |  |  |   Otherwise, the list contains the object's attributes' names, | 
					
						
							|  |  |  |   the names of its class's attributes, | 
					
						
							|  |  |  |   and recursively of the attributes of its class's base classes. | 
					
						
							|  |  |  |   The resulting list is sorted alphabetically. | 
					
						
							|  |  |  |   For example: | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \begin{verbatim} | 
					
						
							| 
									
										
										
										
											2002-02-23 04:40:15 +00:00
										 |  |  | >>> import struct | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | >>> dir() | 
					
						
							| 
									
										
										
										
											2002-02-23 04:40:15 +00:00
										 |  |  | ['__builtins__', '__doc__', '__name__', 'struct'] | 
					
						
							|  |  |  | >>> dir(struct) | 
					
						
							|  |  |  | ['__doc__', '__name__', 'calcsize', 'error', 'pack', 'unpack'] | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											2002-02-23 04:40:15 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \note{Because \function{dir()} is supplied primarily as a convenience | 
					
						
							|  |  |  |   for use at an interactive prompt, | 
					
						
							|  |  |  |   it tries to supply an interesting set of names more than it tries to | 
					
						
							|  |  |  |   supply a rigorously or consistently defined set of names, | 
					
						
							|  |  |  |   and its detailed behavior may change across releases.} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{divmod}{a, b} | 
					
						
							| 
									
										
										
										
											2002-05-21 18:19:49 +00:00
										 |  |  |   Take two (non complex) numbers as arguments and return a pair of numbers | 
					
						
							|  |  |  |   consisting of their quotient and remainder when using long division.  With | 
					
						
							|  |  |  |   mixed operand types, the rules for binary arithmetic operators apply.  For | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   plain and long integers, the result is the same as | 
					
						
							|  |  |  |   \code{(\var{a} / \var{b}, \var{a} \%{} \var{b})}. | 
					
						
							| 
									
										
										
										
											1999-05-06 14:46:35 +00:00
										 |  |  |   For floating point numbers the result is \code{(\var{q}, \var{a} \%{} | 
					
						
							|  |  |  |   \var{b})}, where \var{q} is usually \code{math.floor(\var{a} / | 
					
						
							|  |  |  |   \var{b})} but may be 1 less than that.  In any case \code{\var{q} * | 
					
						
							|  |  |  |   \var{b} + \var{a} \%{} \var{b}} is very close to \var{a}, if | 
					
						
							|  |  |  |   \code{\var{a} \%{} \var{b}} is non-zero it has the same sign as | 
					
						
							|  |  |  |   \var{b}, and \code{0 <= abs(\var{a} \%{} \var{b}) < abs(\var{b})}. | 
					
						
							| 
									
										
										
										
											2002-06-20 21:10:25 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \versionchanged[Using \function{divmod()} with complex numbers is | 
					
						
							|  |  |  |                   deprecated]{2.3} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-04-26 20:29:44 +00:00
										 |  |  | \begin{funcdesc}{enumerate}{iterable} | 
					
						
							|  |  |  |   Return an enumerate object. \var{iterable} must be a sequence, an | 
					
						
							|  |  |  |   iterator, or some other object which supports iteration.  The | 
					
						
							|  |  |  |   \method{next()} method of the iterator returned by | 
					
						
							|  |  |  |   \function{enumerate()} returns a tuple containing a count (from | 
					
						
							|  |  |  |   zero) and the corresponding value obtained from iterating over | 
					
						
							| 
									
										
										
										
											2003-05-10 19:46:39 +00:00
										 |  |  |   \var{iterable}.  \function{enumerate()} is useful for obtaining an | 
					
						
							| 
									
										
										
										
											2002-04-26 20:29:44 +00:00
										 |  |  |   indexed series: \code{(0, seq[0])}, \code{(1, seq[1])}, \code{(2, | 
					
						
							|  |  |  |   seq[2])}, \ldots. | 
					
						
							|  |  |  |   \versionadded{2.3} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{eval}{expression\optional{, globals\optional{, locals}}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   The arguments are a string and two optional dictionaries.  The | 
					
						
							| 
									
										
										
										
											1995-01-10 10:50:24 +00:00
										 |  |  |   \var{expression} argument is parsed and evaluated as a Python | 
					
						
							|  |  |  |   expression (technically speaking, a condition list) using the | 
					
						
							|  |  |  |   \var{globals} and \var{locals} dictionaries as global and local name | 
					
						
							| 
									
										
										
										
											2002-12-17 01:08:06 +00:00
										 |  |  |   space.  If the \var{globals} dictionary is present and lacks | 
					
						
							|  |  |  |   '__builtins__', the current globals are copied into \var{globals} before | 
					
						
							|  |  |  |   \var{expression} is parsed.  This means that \var{expression} | 
					
						
							|  |  |  |   normally has full access to the standard | 
					
						
							|  |  |  |   \refmodule[builtin]{__builtin__} module and restricted environments | 
					
						
							|  |  |  |   are propagated.  If the \var{locals} dictionary is omitted it defaults to | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   the \var{globals} dictionary.  If both dictionaries are omitted, the | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   expression is executed in the environment where \keyword{eval} is | 
					
						
							| 
									
										
										
										
											1995-01-10 10:50:24 +00:00
										 |  |  |   called.  The return value is the result of the evaluated expression. | 
					
						
							|  |  |  |   Syntax errors are reported as exceptions.  Example: | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \begin{verbatim} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | >>> x = 1 | 
					
						
							|  |  |  | >>> print eval('x+1') | 
					
						
							|  |  |  | 2 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   This function can also be used to execute arbitrary code objects | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   (such as those created by \function{compile()}).  In this case pass | 
					
						
							|  |  |  |   a code object instead of a string.  The code object must have been | 
					
						
							|  |  |  |   compiled passing \code{'eval'} as the \var{kind} argument. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1995-03-07 10:14:09 +00:00
										 |  |  |   Hints: dynamic execution of statements is supported by the | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   \keyword{exec} statement.  Execution of statements from a file is | 
					
						
							|  |  |  |   supported by the \function{execfile()} function.  The | 
					
						
							|  |  |  |   \function{globals()} and \function{locals()} functions returns the | 
					
						
							|  |  |  |   current global and local dictionary, respectively, which may be | 
					
						
							|  |  |  |   useful to pass around for use by \function{eval()} or | 
					
						
							|  |  |  |   \function{execfile()}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-07-02 15:31:54 +00:00
										 |  |  | \begin{funcdesc}{execfile}{filename\optional{, globals\optional{, locals}}} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   This function is similar to the | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   \keyword{exec} statement, but parses a file instead of a string.  It | 
					
						
							|  |  |  |   is different from the \keyword{import} statement in that it does not | 
					
						
							|  |  |  |   use the module administration --- it reads the file unconditionally | 
					
						
							|  |  |  |   and does not create a new module.\footnote{It is used relatively | 
					
						
							|  |  |  |   rarely so does not warrant being made into a statement.} | 
					
						
							| 
									
										
										
										
											1995-01-10 10:50:24 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   The arguments are a file name and two optional dictionaries.  The | 
					
						
							|  |  |  |   file is parsed and evaluated as a sequence of Python statements | 
					
						
							|  |  |  |   (similarly to a module) using the \var{globals} and \var{locals} | 
					
						
							| 
									
										
										
										
											2000-09-12 16:23:48 +00:00
										 |  |  |   dictionaries as global and local namespace.  If the \var{locals} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   dictionary is omitted it defaults to the \var{globals} dictionary. | 
					
						
							| 
									
										
										
										
											1995-01-10 10:50:24 +00:00
										 |  |  |   If both dictionaries are omitted, the expression is executed in the | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   environment where \function{execfile()} is called.  The return value is | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   \code{None}. | 
					
						
							| 
									
										
										
										
											2001-09-30 06:32:59 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   \warning{The default \var{locals} act as described for function | 
					
						
							| 
									
										
										
										
											2001-09-30 06:32:59 +00:00
										 |  |  |   \function{locals()} below:  modifications to the default \var{locals} | 
					
						
							|  |  |  |   dictionary should not be attempted.  Pass an explicit \var{locals} | 
					
						
							|  |  |  |   dictionary if you need to see effects of the code on \var{locals} after | 
					
						
							|  |  |  |   function \function{execfile()} returns.  \function{execfile()} cannot | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   be used reliably to modify a function's locals.} | 
					
						
							| 
									
										
										
										
											1995-01-10 10:50:24 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-09-20 19:55:29 +00:00
										 |  |  | \begin{funcdesc}{file}{filename\optional{, mode\optional{, bufsize}}} | 
					
						
							|  |  |  |   Return a new file object (described earlier under Built-in Types). | 
					
						
							|  |  |  |   The first two arguments are the same as for \code{stdio}'s | 
					
						
							|  |  |  |   \cfunction{fopen()}: \var{filename} is the file name to be opened, | 
					
						
							|  |  |  |   \var{mode} indicates how the file is to be opened: \code{'r'} for | 
					
						
							|  |  |  |   reading, \code{'w'} for writing (truncating an existing file), and | 
					
						
							|  |  |  |   \code{'a'} opens it for appending (which on \emph{some} \UNIX{} | 
					
						
							|  |  |  |   systems means that \emph{all} writes append to the end of the file, | 
					
						
							|  |  |  |   regardless of the current seek position). | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   Modes \code{'r+'}, \code{'w+'} and \code{'a+'} open the file for | 
					
						
							|  |  |  |   updating (note that \code{'w+'} truncates the file).  Append | 
					
						
							|  |  |  |   \code{'b'} to the mode to open the file in binary mode, on systems | 
					
						
							|  |  |  |   that differentiate between binary and text files (else it is | 
					
						
							|  |  |  |   ignored).  If the file cannot be opened, \exception{IOError} is | 
					
						
							|  |  |  |   raised. | 
					
						
							| 
									
										
										
										
											2002-05-22 20:39:43 +00:00
										 |  |  |    | 
					
						
							|  |  |  |   In addition to the standard \cfunction{fopen()} values \var{mode} | 
					
						
							|  |  |  |   may be \code{'U'} or \code{'rU'}. If Python is built with universal | 
					
						
							|  |  |  |   newline support (the default) the file is opened as a text file, but | 
					
						
							|  |  |  |   lines may be terminated by any of \code{'\e n'}, the Unix end-of-line | 
					
						
							|  |  |  |   convention, | 
					
						
							|  |  |  |   \code{'\e r'}, the Macintosh convention or \code{'\e r\e n'}, the Windows | 
					
						
							|  |  |  |   convention. All of these external representations are seen as | 
					
						
							|  |  |  |   \code{'\e n'} | 
					
						
							|  |  |  |   by the Python program. If Python is built without universal newline support | 
					
						
							|  |  |  |   \var{mode} \code{'U'} is the same as normal text mode.  Note that | 
					
						
							|  |  |  |   file objects so opened also have an attribute called | 
					
						
							|  |  |  |   \member{newlines} which has a value of \code{None} (if no newlines | 
					
						
							|  |  |  |   have yet been seen), \code{'\e n'}, \code{'\e r'}, \code{'\e r\e n'},  | 
					
						
							|  |  |  |   or a tuple containing all the newline types seen. | 
					
						
							| 
									
										
										
										
											2001-09-20 19:55:29 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   If \var{mode} is omitted, it defaults to \code{'r'}.  When opening a | 
					
						
							|  |  |  |   binary file, you should append \code{'b'} to the \var{mode} value | 
					
						
							|  |  |  |   for improved portability.  (It's useful even on systems which don't | 
					
						
							|  |  |  |   treat binary and text files differently, where it serves as | 
					
						
							|  |  |  |   documentation.) | 
					
						
							|  |  |  |   \index{line-buffered I/O}\index{unbuffered I/O}\index{buffer size, I/O} | 
					
						
							|  |  |  |   \index{I/O control!buffering} | 
					
						
							|  |  |  |   The optional \var{bufsize} argument specifies the | 
					
						
							|  |  |  |   file's desired buffer size: 0 means unbuffered, 1 means line | 
					
						
							|  |  |  |   buffered, any other positive value means use a buffer of | 
					
						
							|  |  |  |   (approximately) that size.  A negative \var{bufsize} means to use | 
					
						
							|  |  |  |   the system default, which is usually line buffered for for tty | 
					
						
							|  |  |  |   devices and fully buffered for other files.  If omitted, the system | 
					
						
							|  |  |  |   default is used.\footnote{ | 
					
						
							|  |  |  |     Specifying a buffer size currently has no effect on systems that | 
					
						
							|  |  |  |     don't have \cfunction{setvbuf()}.  The interface to specify the | 
					
						
							|  |  |  |     buffer size is not done using a method that calls | 
					
						
							|  |  |  |     \cfunction{setvbuf()}, because that may dump core when called | 
					
						
							|  |  |  |     after any I/O has been performed, and there's no reliable way to | 
					
						
							|  |  |  |     determine whether this is the case.} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   The \function{file()} constructor is new in Python 2.2.  The previous | 
					
						
							|  |  |  |   spelling, \function{open()}, is retained for compatibility, and is an | 
					
						
							|  |  |  |   alias for \function{file()}. | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{filter}{function, list} | 
					
						
							| 
									
										
										
										
											2001-05-02 20:19:19 +00:00
										 |  |  |   Construct a list from those elements of \var{list} for which | 
					
						
							|  |  |  |   \var{function} returns true.  \var{list} may be either a sequence, a | 
					
						
							|  |  |  |   container which supports iteration, or an iterator,  If \var{list} | 
					
						
							|  |  |  |   is a string or a tuple, the result also has that type; otherwise it | 
					
						
							|  |  |  |   is always a list.  If \var{function} is \code{None}, the identity | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   function is assumed, that is, all elements of \var{list} that are false | 
					
						
							| 
									
										
										
										
											2001-05-02 20:19:19 +00:00
										 |  |  |   (zero or empty) are removed. | 
					
						
							| 
									
										
										
										
											2003-05-31 08:02:38 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-07-02 12:27:43 +00:00
										 |  |  |   Note that \code{filter(function, \var{list})} is equivalent to | 
					
						
							|  |  |  |   \code{[item for item in \var{list} if function(item)]} if function is | 
					
						
							|  |  |  |   not \code{None} and \code{[item for item in \var{list} if item]} if | 
					
						
							|  |  |  |   function is \code{None}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{float}{\optional{x}} | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   Convert a string or a number to floating point.  If the argument is a | 
					
						
							| 
									
										
										
										
											1998-12-07 17:13:18 +00:00
										 |  |  |   string, it must contain a possibly signed decimal or floating point | 
					
						
							| 
									
										
										
										
											1999-02-18 16:08:36 +00:00
										 |  |  |   number, possibly embedded in whitespace; this behaves identical to | 
					
						
							|  |  |  |   \code{string.atof(\var{x})}.  Otherwise, the argument may be a plain | 
					
						
							|  |  |  |   or long integer or a floating point number, and a floating point | 
					
						
							|  |  |  |   number with the same value (within Python's floating point | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   precision) is returned.  If no argument is given, returns \code{0.0}. | 
					
						
							| 
									
										
										
										
											1999-02-18 16:08:36 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   \note{When passing in a string, values for NaN\index{NaN} | 
					
						
							| 
									
										
										
										
											1999-02-18 16:08:36 +00:00
										 |  |  |   and Infinity\index{Infinity} may be returned, depending on the | 
					
						
							|  |  |  |   underlying C library.  The specific set of strings accepted which | 
					
						
							|  |  |  |   cause these values to be returned depends entirely on the C library | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   and is known to vary.} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1999-07-22 19:21:45 +00:00
										 |  |  | \begin{funcdesc}{getattr}{object, name\optional{, default}} | 
					
						
							|  |  |  |   Return the value of the named attributed of \var{object}.  \var{name} | 
					
						
							|  |  |  |   must be a string.  If the string is the name of one of the object's | 
					
						
							|  |  |  |   attributes, the result is the value of that attribute.  For example, | 
					
						
							|  |  |  |   \code{getattr(x, 'foobar')} is equivalent to \code{x.foobar}.  If the | 
					
						
							|  |  |  |   named attribute does not exist, \var{default} is returned if provided, | 
					
						
							|  |  |  |   otherwise \exception{AttributeError} is raised. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1995-07-07 22:58:28 +00:00
										 |  |  | \begin{funcdesc}{globals}{} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return a dictionary representing the current global symbol table. | 
					
						
							|  |  |  |   This is always the dictionary of the current module (inside a | 
					
						
							|  |  |  |   function or method, this is the module where it is defined, not the | 
					
						
							|  |  |  |   module from which it is called). | 
					
						
							| 
									
										
										
										
											1995-07-07 22:58:28 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{hasattr}{object, name} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   The arguments are an object and a string.  The result is 1 if the | 
					
						
							|  |  |  |   string is the name of one of the object's attributes, 0 if not. | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   (This is implemented by calling \code{getattr(\var{object}, | 
					
						
							|  |  |  |   \var{name})} and seeing whether it raises an exception or not.) | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{hash}{object} | 
					
						
							|  |  |  |   Return the hash value of the object (if it has one).  Hash values | 
					
						
							| 
									
										
										
										
											1997-12-30 20:38:16 +00:00
										 |  |  |   are integers.  They are used to quickly compare dictionary | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   keys during a dictionary lookup.  Numeric values that compare equal | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   have the same hash value (even if they are of different types, as is | 
					
						
							|  |  |  |   the case for 1 and 1.0). | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-12-18 16:31:08 +00:00
										 |  |  | \begin{funcdesc}{help}{\optional{object}} | 
					
						
							|  |  |  |   Invoke the built-in help system.  (This function is intended for | 
					
						
							|  |  |  |   interactive use.)  If no argument is given, the interactive help | 
					
						
							|  |  |  |   system starts on the interpreter console.  If the argument is a | 
					
						
							|  |  |  |   string, then the string is looked up as the name of a module, | 
					
						
							|  |  |  |   function, class, method, keyword, or documentation topic, and a | 
					
						
							|  |  |  |   help page is printed on the console.  If the argument is any other | 
					
						
							|  |  |  |   kind of object, a help page on the object is generated. | 
					
						
							| 
									
										
										
										
											2002-04-17 12:54:04 +00:00
										 |  |  |   \versionadded{2.2} | 
					
						
							| 
									
										
										
										
											2001-12-18 16:31:08 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{hex}{x} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   Convert an integer number (of any size) to a hexadecimal string. | 
					
						
							| 
									
										
										
										
											1997-01-14 18:44:23 +00:00
										 |  |  |   The result is a valid Python expression.  Note: this always yields | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   an unsigned literal.  For example, on a 32-bit machine, | 
					
						
							|  |  |  |   \code{hex(-1)} yields \code{'0xffffffff'}.  When evaluated on a | 
					
						
							|  |  |  |   machine with the same word size, this literal is evaluated as -1; at | 
					
						
							|  |  |  |   a different word size, it may turn up as a large positive number or | 
					
						
							|  |  |  |   raise an \exception{OverflowError} exception. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{id}{object} | 
					
						
							| 
									
										
										
										
											2000-06-29 03:46:46 +00:00
										 |  |  |   Return the `identity' of an object.  This is an integer (or long | 
					
						
							|  |  |  |   integer) which is guaranteed to be unique and constant for this | 
					
						
							|  |  |  |   object during its lifetime.  Two objects whose lifetimes are | 
					
						
							|  |  |  |   disjunct may have the same \function{id()} value.  (Implementation | 
					
						
							|  |  |  |   note: this is the address of the object.) | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-08-08 12:30:22 +00:00
										 |  |  | \begin{funcdesc}{input}{\optional{prompt}} | 
					
						
							| 
									
										
										
										
											1998-06-17 15:16:40 +00:00
										 |  |  |   Equivalent to \code{eval(raw_input(\var{prompt}))}. | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   \warning{This function is not safe from user errors!  It | 
					
						
							| 
									
										
										
										
											2000-09-09 03:33:42 +00:00
										 |  |  |   expects a valid Python expression as input; if the input is not | 
					
						
							|  |  |  |   syntactically valid, a \exception{SyntaxError} will be raised. | 
					
						
							|  |  |  |   Other exceptions may be raised if there is an error during | 
					
						
							|  |  |  |   evaluation.  (On the other hand, sometimes this is exactly what you | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   need when writing a quick script for expert use.)} | 
					
						
							| 
									
										
										
										
											2000-09-09 03:33:42 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   If the \refmodule{readline} module was loaded, then | 
					
						
							| 
									
										
										
										
											2000-09-09 03:33:42 +00:00
										 |  |  |   \function{input()} will use it to provide elaborate line editing and | 
					
						
							|  |  |  |   history features. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   Consider using the \function{raw_input()} function for general input | 
					
						
							|  |  |  |   from users. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{int}{\optional{x\optional{, radix}}} | 
					
						
							| 
									
										
										
										
											2000-02-17 17:45:52 +00:00
										 |  |  |   Convert a string or number to a plain integer.  If the argument is a | 
					
						
							|  |  |  |   string, it must contain a possibly signed decimal number | 
					
						
							| 
									
										
										
										
											2003-05-31 08:02:38 +00:00
										 |  |  |   representable as a Python integer, possibly embedded in whitespace. | 
					
						
							|  |  |  |   The \var{radix} parameter gives the base for the | 
					
						
							| 
									
										
										
										
											2000-11-17 19:44:14 +00:00
										 |  |  |   conversion and may be any integer in the range [2, 36], or zero.  If | 
					
						
							|  |  |  |   \var{radix} is zero, the proper radix is guessed based on the | 
					
						
							|  |  |  |   contents of string; the interpretation is the same as for integer | 
					
						
							|  |  |  |   literals.  If \var{radix} is specified and \var{x} is not a string, | 
					
						
							| 
									
										
										
										
											2000-02-17 17:45:52 +00:00
										 |  |  |   \exception{TypeError} is raised. | 
					
						
							|  |  |  |   Otherwise, the argument may be a plain or | 
					
						
							|  |  |  |   long integer or a floating point number.  Conversion of floating | 
					
						
							| 
									
										
										
										
											2001-07-26 20:02:17 +00:00
										 |  |  |   point numbers to integers truncates (towards zero). | 
					
						
							| 
									
										
										
										
											2002-11-19 20:49:15 +00:00
										 |  |  |   If the argument is outside the integer range a long object will | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   be returned instead.  If no arguments are given, returns \code{0}. | 
					
						
							| 
									
										
										
										
											2000-02-17 17:45:52 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1997-03-03 16:03:27 +00:00
										 |  |  | \begin{funcdesc}{intern}{string} | 
					
						
							|  |  |  |   Enter \var{string} in the table of ``interned'' strings and return | 
					
						
							|  |  |  |   the interned string -- which is \var{string} itself or a copy. | 
					
						
							|  |  |  |   Interning strings is useful to gain a little performance on | 
					
						
							|  |  |  |   dictionary lookup -- if the keys in a dictionary are interned, and | 
					
						
							|  |  |  |   the lookup key is interned, the key comparisons (after hashing) can | 
					
						
							|  |  |  |   be done by a pointer compare instead of a string compare.  Normally, | 
					
						
							|  |  |  |   the names used in Python programs are automatically interned, and | 
					
						
							|  |  |  |   the dictionaries used to hold module, class or instance attributes | 
					
						
							| 
									
										
										
										
											2002-08-19 21:43:18 +00:00
										 |  |  |   have interned keys.  \versionchanged[Interned strings are not | 
					
						
							|  |  |  |   immortal (like they used to be in Python 2.2 and before); | 
					
						
							|  |  |  |   you must keep a reference to the return value of \function{intern()} | 
					
						
							|  |  |  |   around to benefit from it]{2.3} | 
					
						
							| 
									
										
										
										
											1997-03-03 16:03:27 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  | \begin{funcdesc}{isinstance}{object, classinfo} | 
					
						
							|  |  |  |   Return true if the \var{object} argument is an instance of the | 
					
						
							|  |  |  |   \var{classinfo} argument, or of a (direct or indirect) subclass | 
					
						
							|  |  |  |   thereof.  Also return true if \var{classinfo} is a type object and | 
					
						
							|  |  |  |   \var{object} is an object of that type.  If \var{object} is not a | 
					
						
							| 
									
										
										
										
											2003-01-31 17:19:08 +00:00
										 |  |  |   class instance or an object of the given type, the function always | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   returns false.  If \var{classinfo} is neither a class object nor a | 
					
						
							|  |  |  |   type object, it may be a tuple of class or type objects, or may | 
					
						
							|  |  |  |   recursively contain other such tuples (other sequence types are not | 
					
						
							|  |  |  |   accepted).  If \var{classinfo} is not a class, type, or tuple of | 
					
						
							|  |  |  |   classes, types, and such tuples, a \exception{TypeError} exception | 
					
						
							|  |  |  |   is raised. | 
					
						
							|  |  |  |   \versionchanged[Support for a tuple of type information was added]{2.2} | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-12-12 16:41:44 +00:00
										 |  |  | \begin{funcdesc}{issubclass}{class, classinfo} | 
					
						
							|  |  |  |   Return true if \var{class} is a subclass (direct or indirect) of | 
					
						
							|  |  |  |   \var{classinfo}.  A class is considered a subclass of itself. | 
					
						
							|  |  |  |   \var{classinfo} may be a tuple of class objects, in which case every | 
					
						
							|  |  |  |   entry in \var{classinfo} will be checked. In any other case, a | 
					
						
							|  |  |  |   \exception{TypeError} exception is raised. | 
					
						
							|  |  |  |   \versionchanged[Support for a tuple of type information was added]{2.3} | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-09-06 19:04:29 +00:00
										 |  |  | \begin{funcdesc}{iter}{o\optional{, sentinel}} | 
					
						
							|  |  |  |   Return an iterator object.  The first argument is interpreted very | 
					
						
							|  |  |  |   differently depending on the presence of the second argument. | 
					
						
							|  |  |  |   Without a second argument, \var{o} must be a collection object which | 
					
						
							|  |  |  |   supports the iteration protocol (the \method{__iter__()} method), or | 
					
						
							|  |  |  |   it must support the sequence protocol (the \method{__getitem__()} | 
					
						
							|  |  |  |   method with integer arguments starting at \code{0}).  If it does not | 
					
						
							|  |  |  |   support either of those protocols, \exception{TypeError} is raised. | 
					
						
							|  |  |  |   If the second argument, \var{sentinel}, is given, then \var{o} must | 
					
						
							|  |  |  |   be a callable object.  The iterator created in this case will call | 
					
						
							|  |  |  |   \var{o} with no arguments for each call to its \method{next()} | 
					
						
							|  |  |  |   method; if the value returned is equal to \var{sentinel}, | 
					
						
							|  |  |  |   \exception{StopIteration} will be raised, otherwise the value will | 
					
						
							|  |  |  |   be returned. | 
					
						
							|  |  |  |   \versionadded{2.2} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{len}{s} | 
					
						
							|  |  |  |   Return the length (the number of items) of an object.  The argument | 
					
						
							|  |  |  |   may be a sequence (string, tuple or list) or a mapping (dictionary). | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												Generalize dictionary() to accept a sequence of 2-sequences.  At the
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2.  These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object.  For now, I left these
functions file static, so no corresponding doc changes.  It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x".  Got a better name?  "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex:  Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
  iteration, or an iterator object" is getting to be a PITA.  Many
  months ago I suggested factoring this out into "iterable object",
  where the definition of that could include being explicit about
  generators too (as is, I'm not sure a reader outside of PythonLabs
  could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple():  When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
											
										 
											2001-10-26 05:06:50 +00:00
										 |  |  | \begin{funcdesc}{list}{\optional{sequence}} | 
					
						
							| 
									
										
										
										
											2001-05-02 20:19:19 +00:00
										 |  |  |   Return a list whose items are the same and in the same order as | 
					
						
							|  |  |  |   \var{sequence}'s items.  \var{sequence} may be either a sequence, a | 
					
						
							|  |  |  |   container that supports iteration, or an iterator object.  If | 
					
						
							|  |  |  |   \var{sequence} is already a list, a copy is made and returned, | 
					
						
							|  |  |  |   similar to \code{\var{sequence}[:]}.  For instance, | 
					
						
							|  |  |  |   \code{list('abc')} returns \code{['a', 'b', 'c']} and \code{list( | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   (1, 2, 3) )} returns \code{[1, 2, 3]}.  If no argument is given, | 
					
						
							|  |  |  |   returns a new empty list, \code{[]}. | 
					
						
							| 
									
										
										
										
											1997-06-02 17:21:20 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1995-07-07 22:58:28 +00:00
										 |  |  | \begin{funcdesc}{locals}{} | 
					
						
							| 
									
										
										
										
											2003-01-04 02:16:22 +00:00
										 |  |  |   Update and return a dictionary representing the current local symbol table. | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   \warning{The contents of this dictionary should not be modified; | 
					
						
							|  |  |  |   changes may not affect the values of local variables used by the | 
					
						
							|  |  |  |   interpreter.} | 
					
						
							| 
									
										
										
										
											1995-07-07 22:58:28 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{long}{\optional{x\optional{, radix}}} | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   Convert a string or number to a long integer.  If the argument is a | 
					
						
							| 
									
										
										
										
											2001-01-04 05:09:16 +00:00
										 |  |  |   string, it must contain a possibly signed number of | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   arbitrary size, possibly embedded in whitespace; | 
					
						
							| 
									
										
										
										
											2000-11-17 19:44:14 +00:00
										 |  |  |   this behaves identical to \code{string.atol(\var{x})}.  The | 
					
						
							|  |  |  |   \var{radix} argument is interpreted in the same way as for | 
					
						
							|  |  |  |   \function{int()}, and may only be given when \var{x} is a string. | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   Otherwise, the argument may be a plain or | 
					
						
							| 
									
										
										
										
											1997-12-30 20:38:16 +00:00
										 |  |  |   long integer or a floating point number, and a long integer with | 
					
						
							| 
									
										
										
										
											1997-04-02 06:04:02 +00:00
										 |  |  |   the same value is returned.    Conversion of floating | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   point numbers to integers truncates (towards zero).  If no arguments | 
					
						
							|  |  |  |   are given, returns \code{0L}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{map}{function, list, ...} | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   Apply \var{function} to every item of \var{list} and return a list | 
					
						
							|  |  |  |   of the results.  If additional \var{list} arguments are passed, | 
					
						
							|  |  |  |   \var{function} must take that many arguments and is applied to the | 
					
						
							|  |  |  |   items of all lists in parallel; if a list is shorter than another it | 
					
						
							|  |  |  |   is assumed to be extended with \code{None} items.  If \var{function} | 
					
						
							|  |  |  |   is \code{None}, the identity function is assumed; if there are | 
					
						
							|  |  |  |   multiple list arguments, \function{map()} returns a list consisting | 
					
						
							|  |  |  |   of tuples containing the corresponding items from all lists (a kind | 
					
						
							|  |  |  |   of transpose operation).  The \var{list} arguments may be any kind | 
					
						
							|  |  |  |   of sequence; the result is always a list. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-11-25 18:53:05 +00:00
										 |  |  | \begin{funcdesc}{max}{s\optional{, args...}} | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   With a single argument \var{s}, return the largest item of a | 
					
						
							|  |  |  |   non-empty sequence (such as a string, tuple or list).  With more | 
					
						
							|  |  |  |   than one argument, return the largest of the arguments. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-11-25 18:53:05 +00:00
										 |  |  | \begin{funcdesc}{min}{s\optional{, args...}} | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   With a single argument \var{s}, return the smallest item of a | 
					
						
							|  |  |  |   non-empty sequence (such as a string, tuple or list).  With more | 
					
						
							|  |  |  |   than one argument, return the smallest of the arguments. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 09:15:26 +00:00
										 |  |  | \begin{funcdesc}{object}{} | 
					
						
							| 
									
										
										
										
											2003-06-26 03:11:57 +00:00
										 |  |  |   Return a new featureless object.  \function{object()} is a base  | 
					
						
							|  |  |  |   for all new style classes.  It has the methods that are common | 
					
						
							|  |  |  |   to all instances of new style classes. | 
					
						
							|  |  |  |   \versionadded{2.2} | 
					
						
							| 
									
										
										
										
											2003-06-11 09:15:26 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-26 03:11:57 +00:00
										 |  |  |   \versionchanged[This function does not accept any arguments. | 
					
						
							|  |  |  |   Formerly, it accepted arguments but ignored them]{2.3} | 
					
						
							| 
									
										
										
										
											2003-06-11 09:15:26 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{oct}{x} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  |   Convert an integer number (of any size) to an octal string.  The | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   result is a valid Python expression.  Note: this always yields an | 
					
						
							|  |  |  |   unsigned literal.  For example, on a 32-bit machine, \code{oct(-1)} | 
					
						
							|  |  |  |   yields \code{'037777777777'}.  When evaluated on a machine with the | 
					
						
							|  |  |  |   same word size, this literal is evaluated as -1; at a different word | 
					
						
							| 
									
										
										
										
											1997-01-14 18:44:23 +00:00
										 |  |  |   size, it may turn up as a large positive number or raise an | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   \exception{OverflowError} exception. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{open}{filename\optional{, mode\optional{, bufsize}}} | 
					
						
							| 
									
										
										
										
											2001-09-20 19:55:29 +00:00
										 |  |  |   An alias for the \function{file()} function above. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{ord}{c} | 
					
						
							| 
									
										
										
										
											2000-04-06 14:43:12 +00:00
										 |  |  |   Return the \ASCII{} value of a string of one character or a Unicode | 
					
						
							|  |  |  |   character.  E.g., \code{ord('a')} returns the integer \code{97}, | 
					
						
							|  |  |  |   \code{ord(u'\\u2020')} returns \code{8224}.  This is the inverse of | 
					
						
							|  |  |  |   \function{chr()} for strings and of \function{unichr()} for Unicode | 
					
						
							|  |  |  |   characters. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{pow}{x, y\optional{, z}} | 
					
						
							| 
									
										
										
										
											1994-08-12 13:13:50 +00:00
										 |  |  |   Return \var{x} to the power \var{y}; if \var{z} is present, return | 
					
						
							|  |  |  |   \var{x} to the power \var{y}, modulo \var{z} (computed more | 
					
						
							| 
									
										
										
										
											2001-07-12 11:27:16 +00:00
										 |  |  |   efficiently than \code{pow(\var{x}, \var{y}) \%\ \var{z}}).  The | 
					
						
							|  |  |  |   arguments must have numeric types.  With mixed operand types, the | 
					
						
							|  |  |  |   coercion rules for binary arithmetic operators apply.  For int and | 
					
						
							|  |  |  |   long int operands, the result has the same type as the operands | 
					
						
							|  |  |  |   (after coercion) unless the second argument is negative; in that | 
					
						
							|  |  |  |   case, all arguments are converted to float and a float result is | 
					
						
							|  |  |  |   delivered.  For example, \code{10**2} returns \code{100}, but | 
					
						
							|  |  |  |   \code{10**-2} returns \code{0.01}.  (This last feature was added in | 
					
						
							| 
									
										
										
										
											2001-09-03 08:35:41 +00:00
										 |  |  |   Python 2.2.  In Python 2.1 and before, if both arguments were of integer | 
					
						
							|  |  |  |   types and the second argument was negative, an exception was raised.) | 
					
						
							| 
									
										
										
										
											2001-09-20 19:55:29 +00:00
										 |  |  |   If the second argument is negative, the third argument must be omitted. | 
					
						
							| 
									
										
										
										
											2001-09-03 08:35:41 +00:00
										 |  |  |   If \var{z} is present, \var{x} and \var{y} must be of integer types, | 
					
						
							|  |  |  |   and \var{y} must be non-negative.  (This restriction was added in | 
					
						
							|  |  |  |   Python 2.2.  In Python 2.1 and before, floating 3-argument \code{pow()} | 
					
						
							|  |  |  |   returned platform-dependent results depending on floating-point | 
					
						
							|  |  |  |   rounding accidents.) | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-05-10 19:46:39 +00:00
										 |  |  | \begin{funcdesc}{property}{\optional{fget\optional{, fset\optional{, | 
					
						
							|  |  |  |                            fdel\optional{, doc}}}}} | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  |   Return a property attribute for new-style classes (classes that | 
					
						
							| 
									
										
										
										
											2003-05-10 19:46:39 +00:00
										 |  |  |   derive from \class{object}). | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   \var{fget} is a function for getting an attribute value, likewise | 
					
						
							|  |  |  |   \var{fset} is a function for setting, and \var{fdel} a function | 
					
						
							|  |  |  |   for del'ing, an attribute.  Typical use is to define a managed attribute x: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{verbatim} | 
					
						
							|  |  |  | class C(object): | 
					
						
							|  |  |  |     def getx(self): return self.__x | 
					
						
							|  |  |  |     def setx(self, value): self.__x = value | 
					
						
							|  |  |  |     def delx(self): del self.__x | 
					
						
							| 
									
										
										
										
											2003-07-05 17:37:58 +00:00
										 |  |  |     x = property(getx, setx, delx, "I'm the 'x' property.") | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | \end{verbatim} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   \versionadded{2.2} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{range}{\optional{start,} stop\optional{, step}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   This is a versatile function to create lists containing arithmetic | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   progressions.  It is most often used in \keyword{for} loops.  The | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   arguments must be plain integers.  If the \var{step} argument is | 
					
						
							|  |  |  |   omitted, it defaults to \code{1}.  If the \var{start} argument is | 
					
						
							|  |  |  |   omitted, it defaults to \code{0}.  The full form returns a list of | 
					
						
							|  |  |  |   plain integers \code{[\var{start}, \var{start} + \var{step}, | 
					
						
							|  |  |  |   \var{start} + 2 * \var{step}, \ldots]}.  If \var{step} is positive, | 
					
						
							|  |  |  |   the last element is the largest \code{\var{start} + \var{i} * | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  |   \var{step}} less than \var{stop}; if \var{step} is negative, the last | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   element is the largest \code{\var{start} + \var{i} * \var{step}} | 
					
						
							| 
									
										
										
										
											1998-04-03 07:15:54 +00:00
										 |  |  |   greater than \var{stop}.  \var{step} must not be zero (or else | 
					
						
							|  |  |  |   \exception{ValueError} is raised).  Example: | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \begin{verbatim} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | >>> range(10) | 
					
						
							|  |  |  | [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] | 
					
						
							|  |  |  | >>> range(1, 11) | 
					
						
							|  |  |  | [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] | 
					
						
							|  |  |  | >>> range(0, 30, 5) | 
					
						
							|  |  |  | [0, 5, 10, 15, 20, 25] | 
					
						
							|  |  |  | >>> range(0, 10, 3) | 
					
						
							|  |  |  | [0, 3, 6, 9] | 
					
						
							|  |  |  | >>> range(0, -10, -1) | 
					
						
							|  |  |  | [0, -1, -2, -3, -4, -5, -6, -7, -8, -9] | 
					
						
							|  |  |  | >>> range(0) | 
					
						
							|  |  |  | [] | 
					
						
							|  |  |  | >>> range(1, 0) | 
					
						
							|  |  |  | [] | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-08-08 12:30:22 +00:00
										 |  |  | \begin{funcdesc}{raw_input}{\optional{prompt}} | 
					
						
							|  |  |  |   If the \var{prompt} argument is present, it is written to standard output | 
					
						
							|  |  |  |   without a trailing newline.  The function then reads a line from input, | 
					
						
							|  |  |  |   converts it to a string (stripping a trailing newline), and returns that. | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   When \EOF{} is read, \exception{EOFError} is raised. Example: | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \begin{verbatim} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | >>> s = raw_input('--> ') | 
					
						
							|  |  |  | --> Monty Python's Flying Circus | 
					
						
							|  |  |  | >>> s | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | "Monty Python's Flying Circus" | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											1997-06-02 17:21:20 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   If the \refmodule{readline} module was loaded, then | 
					
						
							|  |  |  |   \function{raw_input()} will use it to provide elaborate | 
					
						
							|  |  |  |   line editing and history features. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1999-01-06 23:10:51 +00:00
										 |  |  | \begin{funcdesc}{reduce}{function, sequence\optional{, initializer}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Apply \var{function} of two arguments cumulatively to the items of | 
					
						
							|  |  |  |   \var{sequence}, from left to right, so as to reduce the sequence to | 
					
						
							| 
									
										
										
										
											2002-07-17 13:55:33 +00:00
										 |  |  |   a single value.  For example, \code{reduce(lambda x, y: x+y, [1, 2, | 
					
						
							|  |  |  |   3, 4, 5])} calculates \code{((((1+2)+3)+4)+5)}.  If the optional | 
					
						
							|  |  |  |   \var{initializer} is present, it is placed before the items of the | 
					
						
							|  |  |  |   sequence in the calculation, and serves as a default when the | 
					
						
							|  |  |  |   sequence is empty.  If \var{initializer} is not given and | 
					
						
							|  |  |  |   \var{sequence} contains only one item, the first item is returned. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{reload}{module} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Re-parse and re-initialize an already imported \var{module}.  The | 
					
						
							|  |  |  |   argument must be a module object, so it must have been successfully | 
					
						
							|  |  |  |   imported before.  This is useful if you have edited the module | 
					
						
							|  |  |  |   source file using an external editor and want to try out the new | 
					
						
							|  |  |  |   version without leaving the Python interpreter.  The return value is | 
					
						
							|  |  |  |   the module object (the same as the \var{module} argument). | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   There are a number of caveats: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   If a module is syntactically correct but its initialization fails, | 
					
						
							|  |  |  |   the first \keyword{import} statement for it does not bind its name | 
					
						
							|  |  |  |   locally, but does store a (partially initialized) module object in | 
					
						
							|  |  |  |   \code{sys.modules}.  To reload the module you must first | 
					
						
							|  |  |  |   \keyword{import} it again (this will bind the name to the partially | 
					
						
							|  |  |  |   initialized module object) before you can \function{reload()} it. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   When a module is reloaded, its dictionary (containing the module's | 
					
						
							|  |  |  |   global variables) is retained.  Redefinitions of names will override | 
					
						
							|  |  |  |   the old definitions, so this is generally not a problem.  If the new | 
					
						
							|  |  |  |   version of a module does not define a name that was defined by the | 
					
						
							|  |  |  |   old version, the old definition remains.  This feature can be used | 
					
						
							|  |  |  |   to the module's advantage if it maintains a global table or cache of | 
					
						
							|  |  |  |   objects --- with a \keyword{try} statement it can test for the | 
					
						
							|  |  |  |   table's presence and skip its initialization if desired. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   It is legal though generally not very useful to reload built-in or | 
					
						
							|  |  |  |   dynamically loaded modules, except for \refmodule{sys}, | 
					
						
							|  |  |  |   \refmodule[main]{__main__} and \refmodule[builtin]{__builtin__}.  In | 
					
						
							|  |  |  |   many cases, however, extension modules are not designed to be | 
					
						
							|  |  |  |   initialized more than once, and may fail in arbitrary ways when | 
					
						
							|  |  |  |   reloaded. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   If a module imports objects from another module using \keyword{from} | 
					
						
							|  |  |  |   \ldots{} \keyword{import} \ldots{}, calling \function{reload()} for | 
					
						
							|  |  |  |   the other module does not redefine the objects imported from it --- | 
					
						
							|  |  |  |   one way around this is to re-execute the \keyword{from} statement, | 
					
						
							|  |  |  |   another is to use \keyword{import} and qualified names | 
					
						
							|  |  |  |   (\var{module}.\var{name}) instead. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   If a module instantiates instances of a class, reloading the module | 
					
						
							|  |  |  |   that defines the class does not affect the method definitions of the | 
					
						
							|  |  |  |   instances --- they continue to use the old class definition.  The | 
					
						
							|  |  |  |   same is true for derived classes. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{repr}{object} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return a string containing a printable representation of an object. | 
					
						
							|  |  |  |   This is the same value yielded by conversions (reverse quotes). | 
					
						
							|  |  |  |   It is sometimes useful to be able to access this operation as an | 
					
						
							|  |  |  |   ordinary function.  For many types, this function makes an attempt | 
					
						
							|  |  |  |   to return a string that would yield an object with the same value | 
					
						
							|  |  |  |   when passed to \function{eval()}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-08-24 20:30:07 +00:00
										 |  |  | \begin{funcdesc}{round}{x\optional{, n}} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Return the floating point value \var{x} rounded to \var{n} digits | 
					
						
							|  |  |  |   after the decimal point.  If \var{n} is omitted, it defaults to zero. | 
					
						
							|  |  |  |   The result is a floating point number.  Values are rounded to the | 
					
						
							|  |  |  |   closest multiple of 10 to the power minus \var{n}; if two multiples | 
					
						
							| 
									
										
										
										
											2001-07-06 19:28:48 +00:00
										 |  |  |   are equally close, rounding is done away from 0 (so. for example, | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   \code{round(0.5)} is \code{1.0} and \code{round(-0.5)} is \code{-1.0}). | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{setattr}{object, name, value} | 
					
						
							| 
									
										
										
										
											1998-03-03 21:56:15 +00:00
										 |  |  |   This is the counterpart of \function{getattr()}.  The arguments are an | 
					
						
							| 
									
										
										
										
											1998-08-24 20:30:07 +00:00
										 |  |  |   object, a string and an arbitrary value.  The string may name an | 
					
						
							|  |  |  |   existing attribute or a new attribute.  The function assigns the | 
					
						
							|  |  |  |   value to the attribute, provided the object allows it.  For example, | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   \code{setattr(\var{x}, '\var{foobar}', 123)} is equivalent to | 
					
						
							|  |  |  |   \code{\var{x}.\var{foobar} = 123}. | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{slice}{\optional{start,} stop\optional{, step}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return a slice object representing the set of indices specified by | 
					
						
							|  |  |  |   \code{range(\var{start}, \var{stop}, \var{step})}.  The \var{start} | 
					
						
							| 
									
										
										
										
											2003-07-02 12:27:43 +00:00
										 |  |  |   and \var{step} arguments default to \code{None}.  Slice objects have | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   read-only data attributes \member{start}, \member{stop} and | 
					
						
							|  |  |  |   \member{step} which merely return the argument values (or their | 
					
						
							|  |  |  |   default).  They have no other explicit functionality; however they | 
					
						
							|  |  |  |   are used by Numerical Python\index{Numerical Python} and other third | 
					
						
							|  |  |  |   party extensions.  Slice objects are also generated when extended | 
					
						
							|  |  |  |   indexing syntax is used.  For example: \samp{a[start:stop:step]} or | 
					
						
							|  |  |  |   \samp{a[start:stop, i]}. | 
					
						
							| 
									
										
										
										
											1997-10-05 18:53:00 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | \begin{funcdesc}{staticmethod}{function} | 
					
						
							|  |  |  |   Return a static method for \var{function}. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   A static method does not receive an implicit first argument. | 
					
						
							|  |  |  |   To declare a static method, use this idiom: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{verbatim} | 
					
						
							|  |  |  | class C: | 
					
						
							|  |  |  |     def f(arg1, arg2, ...): ... | 
					
						
							|  |  |  |     f = staticmethod(f) | 
					
						
							|  |  |  | \end{verbatim} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   It can be called either on the class (such as \code{C.f()}) or on an | 
					
						
							|  |  |  |   instance (such as \code{C().f()}).  The instance is ignored except | 
					
						
							|  |  |  |   for its class. | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-26 03:11:57 +00:00
										 |  |  |   Static methods in Python are similar to those found in Java or \Cpp. | 
					
						
							|  |  |  |   For a more advanced concept, see \function{classmethod()} in this | 
					
						
							|  |  |  |   section. | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  |   \versionadded{2.2} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-04-22 14:52:08 +00:00
										 |  |  | \begin{funcdesc}{sum}{sequence\optional{, start}} | 
					
						
							|  |  |  |   Sums \var{start} and the items of a \var{sequence}, from left to | 
					
						
							|  |  |  |   right, and returns the total.  \var{start} defaults to \code{0}. | 
					
						
							|  |  |  |   The \var{sequence}'s items are normally numbers, and are not allowed | 
					
						
							|  |  |  |   to be strings.  The fast, correct way to concatenate sequence of | 
					
						
							|  |  |  |   strings is by calling \code{''.join(\var{sequence})}. | 
					
						
							| 
									
										
										
										
											2003-07-02 12:27:43 +00:00
										 |  |  |   Note that \code{sum(range(\var{n}), \var{m})} is equivalent to | 
					
						
							|  |  |  |   \code{reduce(operator.add, range(\var{n}), \var{m})} | 
					
						
							| 
									
										
										
										
											2003-04-22 08:12:33 +00:00
										 |  |  |   \versionadded{2.3} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | \begin{funcdesc}{super}{type\optional{object-or-type}} | 
					
						
							|  |  |  |   Return the superclass of \var{type}.  If the second argument is omitted | 
					
						
							|  |  |  |   the super object returned is unbound.  If the second argument is an | 
					
						
							| 
									
										
										
										
											2003-07-01 16:31:26 +00:00
										 |  |  |   object, \code{isinstance(\var{obj}, \var{type})} must be true.  If | 
					
						
							|  |  |  |   the second argument is a type, \code{issubclass(\var{type2}, | 
					
						
							|  |  |  |   \var{type})} must be true. | 
					
						
							|  |  |  |   \function{super()} only works for new-style classes. | 
					
						
							| 
									
										
										
										
											2002-12-17 01:02:57 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   A typical use for calling a cooperative superclass method is: | 
					
						
							|  |  |  | \begin{verbatim} | 
					
						
							|  |  |  | class C(B): | 
					
						
							|  |  |  |     def meth(self, arg): | 
					
						
							|  |  |  |         super(C, self).meth(arg) | 
					
						
							|  |  |  | \end{verbatim} | 
					
						
							|  |  |  | \versionadded{2.2} | 
					
						
							|  |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{str}{\optional{object}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return a string containing a nicely printable representation of an | 
					
						
							|  |  |  |   object.  For strings, this returns the string itself.  The | 
					
						
							|  |  |  |   difference with \code{repr(\var{object})} is that | 
					
						
							|  |  |  |   \code{str(\var{object})} does not always attempt to return a string | 
					
						
							|  |  |  |   that is acceptable to \function{eval()}; its goal is to return a | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   printable string.  If no argument is given, returns the empty | 
					
						
							|  |  |  |   string, \code{''}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												Generalize dictionary() to accept a sequence of 2-sequences.  At the
outer level, the iterator protocol is used for memory-efficiency (the
outer sequence may be very large if fully materialized); at the inner
level, PySequence_Fast() is used for time-efficiency (these should
always be sequences of length 2).
dictobject.c, new functions PyDict_{Merge,Update}FromSeq2.  These are
wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2-
sequences argument instead of a mapping object.  For now, I left these
functions file static, so no corresponding doc changes.  It's tempting
to change dict.update() to allow a sequence-of-2-seqs argument too.
Also changed the name of dictionary's keyword argument from "mapping"
to "x".  Got a better name?  "mapping_or_sequence_of_pairs" isn't
attractive, although more so than "mosop" <wink>.
abstract.h, abstract.tex:  Added new PySequence_Fast_GET_SIZE function,
much faster than going thru the all-purpose PySequence_Size.
libfuncs.tex:
- Document dictionary().
- Fiddle tuple() and list() to admit that their argument is optional.
- The long-winded repetitions of "a sequence, a container that supports
  iteration, or an iterator object" is getting to be a PITA.  Many
  months ago I suggested factoring this out into "iterable object",
  where the definition of that could include being explicit about
  generators too (as is, I'm not sure a reader outside of PythonLabs
  could guess that "an iterator object" includes a generator call).
- Please check my curly braces -- I'm going blind <0.9 wink>.
abstract.c, PySequence_Tuple():  When PyObject_GetIter() fails, leave
its error msg alone now (the msg it produces has improved since
PySequence_Tuple was generalized to accept iterable objects, and
PySequence_Tuple was also stomping on the msg in cases it shouldn't
have even before PyObject_GetIter grew a better msg).
											
										 
											2001-10-26 05:06:50 +00:00
										 |  |  | \begin{funcdesc}{tuple}{\optional{sequence}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return a tuple whose items are the same and in the same order as | 
					
						
							|  |  |  |   \var{sequence}'s items.  \var{sequence} may be a sequence, a | 
					
						
							|  |  |  |   container that supports iteration, or an iterator object. | 
					
						
							|  |  |  |   If \var{sequence} is already a tuple, it | 
					
						
							|  |  |  |   is returned unchanged.  For instance, \code{tuple('abc')} returns | 
					
						
							|  |  |  |   returns \code{('a', 'b', 'c')} and \code{tuple([1, 2, 3])} returns | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  |   \code{(1, 2, 3)}.  If no argument is given, returns a new empty | 
					
						
							|  |  |  |   tuple, \code{()}. | 
					
						
							| 
									
										
										
										
											1994-08-12 13:13:50 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \begin{funcdesc}{type}{object} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return the type of an \var{object}.  The return value is a | 
					
						
							|  |  |  |   type\obindex{type} object.  The standard module | 
					
						
							|  |  |  |   \module{types}\refstmodindex{types} defines names for all built-in | 
					
						
							| 
									
										
										
										
											2002-11-01 21:33:44 +00:00
										 |  |  |   types that don't already have built-in names. | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   For instance: | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \begin{verbatim} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | >>> import types | 
					
						
							| 
									
										
										
										
											2002-11-01 21:33:44 +00:00
										 |  |  | >>> x = 'abc' | 
					
						
							|  |  |  | >>> if type(x) is str: print "It's a string" | 
					
						
							|  |  |  | ... | 
					
						
							|  |  |  | It's a string | 
					
						
							|  |  |  | >>> def f(): pass | 
					
						
							|  |  |  | ... | 
					
						
							|  |  |  | >>> if type(f) is types.FunctionType: print "It's a function" | 
					
						
							|  |  |  | ... | 
					
						
							|  |  |  | It's a function | 
					
						
							| 
									
										
										
										
											1998-02-13 06:58:54 +00:00
										 |  |  | \end{verbatim} | 
					
						
							| 
									
										
										
										
											2002-11-01 21:33:44 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  |   The \function{isinstance()} built-in function is recommended for | 
					
						
							|  |  |  |   testing the type of an object. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							| 
									
										
										
										
											1994-02-24 11:28:27 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-04-06 14:43:12 +00:00
										 |  |  | \begin{funcdesc}{unichr}{i} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Return the Unicode string of one character whose Unicode code is the | 
					
						
							|  |  |  |   integer \var{i}.  For example, \code{unichr(97)} returns the string | 
					
						
							|  |  |  |   \code{u'a'}.  This is the inverse of \function{ord()} for Unicode | 
					
						
							|  |  |  |   strings.  The argument must be in the range [0..65535], inclusive. | 
					
						
							|  |  |  |   \exception{ValueError} is raised otherwise. | 
					
						
							|  |  |  |   \versionadded{2.0} | 
					
						
							| 
									
										
										
										
											2000-04-06 14:43:12 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-06-11 08:16:06 +00:00
										 |  |  | \begin{funcdesc}{unicode}{\optional{object\optional{, encoding | 
					
						
							|  |  |  | 				    \optional{, errors}}}} | 
					
						
							| 
									
										
										
										
											2001-10-19 12:02:29 +00:00
										 |  |  |   Return the Unicode string version of \var{object} using one of the | 
					
						
							|  |  |  |   following modes: | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   If \var{encoding} and/or \var{errors} are given, \code{unicode()} | 
					
						
							|  |  |  |   will decode the object which can either be an 8-bit string or a | 
					
						
							|  |  |  |   character buffer using the codec for \var{encoding}. The | 
					
						
							| 
									
										
										
										
											2002-07-09 05:25:46 +00:00
										 |  |  |   \var{encoding} parameter is a string giving the name of an encoding; | 
					
						
							|  |  |  |   if the encoding is not known, \exception{LookupError} is raised. | 
					
						
							| 
									
										
										
										
											2001-10-19 12:02:29 +00:00
										 |  |  |   Error handling is done according to \var{errors}; this specifies the | 
					
						
							|  |  |  |   treatment of characters which are invalid in the input encoding.  If | 
					
						
							|  |  |  |   \var{errors} is \code{'strict'} (the default), a | 
					
						
							|  |  |  |   \exception{ValueError} is raised on errors, while a value of | 
					
						
							|  |  |  |   \code{'ignore'} causes errors to be silently ignored, and a value of | 
					
						
							|  |  |  |   \code{'replace'} causes the official Unicode replacement character, | 
					
						
							|  |  |  |   \code{U+FFFD}, to be used to replace input characters which cannot | 
					
						
							|  |  |  |   be decoded.  See also the \refmodule{codecs} module. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   If no optional parameters are given, \code{unicode()} will mimic the | 
					
						
							|  |  |  |   behaviour of \code{str()} except that it returns Unicode strings | 
					
						
							| 
									
										
										
										
											2002-07-08 14:29:05 +00:00
										 |  |  |   instead of 8-bit strings. More precisely, if \var{object} is a | 
					
						
							|  |  |  |   Unicode string or subclass it will return that Unicode string without | 
					
						
							| 
									
										
										
										
											2002-06-29 16:06:47 +00:00
										 |  |  |   any additional decoding applied. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |   For objects which provide a \method{__unicode__()} method, it will | 
					
						
							|  |  |  |   call this method without arguments to create a Unicode string. For | 
					
						
							|  |  |  |   all other objects, the 8-bit string version or representation is | 
					
						
							|  |  |  |   requested and then converted to a Unicode string using the codec for | 
					
						
							|  |  |  |   the default encoding in \code{'strict'} mode. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   \versionadded{2.0} | 
					
						
							| 
									
										
										
										
											2002-06-29 16:06:47 +00:00
										 |  |  |   \versionchanged[Support for \method{__unicode__()} added]{2.2} | 
					
						
							| 
									
										
										
										
											2000-04-06 14:43:12 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1995-03-13 10:03:32 +00:00
										 |  |  | \begin{funcdesc}{vars}{\optional{object}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   Without arguments, return a dictionary corresponding to the current | 
					
						
							|  |  |  |   local symbol table.  With a module, class or class instance object | 
					
						
							|  |  |  |   as argument (or anything else that has a \member{__dict__} | 
					
						
							|  |  |  |   attribute), returns a dictionary corresponding to the object's | 
					
						
							|  |  |  |   symbol table.  The returned dictionary should not be modified: the | 
					
						
							|  |  |  |   effects on the corresponding symbol table are undefined.\footnote{ | 
					
						
							|  |  |  |     In the current implementation, local variable bindings cannot | 
					
						
							|  |  |  |     normally be affected this way, but variables retrieved from | 
					
						
							|  |  |  |     other scopes (such as modules) can be.  This may change.} | 
					
						
							| 
									
										
										
										
											1994-04-21 10:32:28 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-17 06:33:25 +00:00
										 |  |  | \begin{funcdesc}{xrange}{\optional{start,} stop\optional{, step}} | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   This function is very similar to \function{range()}, but returns an | 
					
						
							|  |  |  |   ``xrange object'' instead of a list.  This is an opaque sequence | 
					
						
							|  |  |  |   type which yields the same values as the corresponding list, without | 
					
						
							|  |  |  |   actually storing them all simultaneously.  The advantage of | 
					
						
							|  |  |  |   \function{xrange()} over \function{range()} is minimal (since | 
					
						
							|  |  |  |   \function{xrange()} still has to create the values when asked for | 
					
						
							|  |  |  |   them) except when a very large range is used on a memory-starved | 
					
						
							|  |  |  |   machine or when all of the range's elements are never used (such as | 
					
						
							|  |  |  |   when the loop is usually terminated with \keyword{break}). | 
					
						
							| 
									
										
										
										
											1994-02-24 11:28:27 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							| 
									
										
										
										
											2000-08-03 15:46:17 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-08-03 17:29:13 +00:00
										 |  |  | \begin{funcdesc}{zip}{seq1, \moreargs} | 
					
						
							| 
									
										
										
										
											2001-12-03 18:35:05 +00:00
										 |  |  |   This function returns a list of tuples, where the \var{i}-th tuple contains | 
					
						
							| 
									
										
										
										
											2001-10-09 19:31:08 +00:00
										 |  |  |   the \var{i}-th element from each of the argument sequences.  At | 
					
						
							|  |  |  |   least one sequence is required, otherwise a \exception{TypeError} is | 
					
						
							|  |  |  |   raised.  The returned list is truncated in length to the length of | 
					
						
							|  |  |  |   the shortest argument sequence.  When there are multiple argument | 
					
						
							|  |  |  |   sequences which are all of the same length, \function{zip()} is | 
					
						
							|  |  |  |   similar to \function{map()} with an initial argument of \code{None}. | 
					
						
							|  |  |  |   With a single sequence argument, it returns a list of 1-tuples. | 
					
						
							|  |  |  |   \versionadded{2.0} | 
					
						
							| 
									
										
										
										
											2000-08-03 17:29:13 +00:00
										 |  |  | \end{funcdesc} |