| 
									
										
										
										
											1998-08-10 19:42:37 +00:00
										 |  |  | \section{\module{marshal} --- | 
					
						
							| 
									
										
										
										
											1999-02-19 22:33:51 +00:00
										 |  |  |          Alternate Python object serialization} | 
					
						
							| 
									
										
										
										
											1998-07-23 17:59:49 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1999-04-22 21:23:22 +00:00
										 |  |  | \declaremodule{builtin}{marshal} | 
					
						
							| 
									
										
										
										
											1998-08-10 19:42:37 +00:00
										 |  |  | \modulesynopsis{Convert Python objects to streams of bytes and back | 
					
						
							| 
									
										
										
										
											1999-04-22 21:23:22 +00:00
										 |  |  |                 (with different constraints).} | 
					
						
							| 
									
										
										
										
											1998-07-23 17:59:49 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-08 06:28:00 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | This module contains functions that can read and write Python | 
					
						
							|  |  |  | values in a binary format.  The format is specific to Python, but | 
					
						
							|  |  |  | independent of machine architecture issues (e.g., you can write a | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | Python value to a file on a PC, transport the file to a Sun, and read | 
					
						
							|  |  |  | it back there).  Details of the format are undocumented on purpose; | 
					
						
							| 
									
										
										
										
											1999-04-05 21:59:15 +00:00
										 |  |  | it may change between Python versions (although it rarely | 
					
						
							|  |  |  | does).\footnote{The name of this module stems from a bit of | 
					
						
							|  |  |  |   terminology used by the designers of Modula-3 (amongst others), who | 
					
						
							|  |  |  |   use the term ``marshalling'' for shipping of data around in a | 
					
						
							|  |  |  |   self-contained form. Strictly speaking, ``to marshal'' means to | 
					
						
							|  |  |  |   convert some data from internal to external form (in an RPC buffer for | 
					
						
							|  |  |  |   instance) and ``unmarshalling'' for the reverse process.} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-07-16 19:01:10 +00:00
										 |  |  | This is not a general ``persistence'' module.  For general persistence | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | and transfer of Python objects through RPC calls, see the modules | 
					
						
							| 
									
										
										
										
											1999-04-22 21:23:22 +00:00
										 |  |  | \refmodule{pickle} and \refmodule{shelve}.  The \module{marshal} module exists | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | mainly to support reading and writing the ``pseudo-compiled'' code for | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  | Python modules of \file{.pyc} files. | 
					
						
							| 
									
										
										
										
											1997-12-15 21:56:05 +00:00
										 |  |  | \refstmodindex{pickle} | 
					
						
							|  |  |  | \refstmodindex{shelve} | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | \obindex{code} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | Not all Python object types are supported; in general, only objects | 
					
						
							|  |  |  | whose value is independent from a particular invocation of Python can | 
					
						
							|  |  |  | be written and read by this module.  The following types are supported: | 
					
						
							|  |  |  | \code{None}, integers, long integers, floating point numbers, | 
					
						
							| 
									
										
										
										
											2000-04-06 14:47:20 +00:00
										 |  |  | strings, Unicode objects, tuples, lists, dictionaries, and code | 
					
						
							|  |  |  | objects, where it should be understood that tuples, lists and | 
					
						
							|  |  |  | dictionaries are only supported as long as the values contained | 
					
						
							|  |  |  | therein are themselves supported; and recursive lists and dictionaries | 
					
						
							|  |  |  | should not be written (they will cause infinite loops). | 
					
						
							| 
									
										
										
										
											1995-03-17 16:07:09 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-01-14 14:51:31 +00:00
										 |  |  | \strong{Caveat:} On machines where C's \code{long int} type has more than | 
					
						
							| 
									
										
										
										
											2001-09-14 20:40:13 +00:00
										 |  |  | 32 bits (such as the DEC Alpha), it is possible to create plain Python | 
					
						
							|  |  |  | integers that are longer than 32 bits. | 
					
						
							|  |  |  | If such an integer is marshaled and read back in on a machine where | 
					
						
							|  |  |  | C's \code{long int} type has only 32 bits, a Python long integer object | 
					
						
							|  |  |  | is returned instead.  While of a different type, the numeric value is | 
					
						
							|  |  |  | the same.  (This behavior is new in Python 2.2.  In earlier versions, | 
					
						
							|  |  |  | all but the least-significant 32 bits of the value were lost, and a | 
					
						
							|  |  |  | warning message was printed.) | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | There are functions that read/write files as well as functions | 
					
						
							|  |  |  | operating on strings. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | The module defines these functions: | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-08 06:28:00 +00:00
										 |  |  | \begin{funcdesc}{dump}{value, file} | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  |   Write the value on the open file.  The value must be a supported | 
					
						
							|  |  |  |   type.  The file must be an open file object such as | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   \code{sys.stdout} or returned by \function{open()} or | 
					
						
							| 
									
										
										
										
											2000-04-03 20:13:55 +00:00
										 |  |  |   \function{posix.popen()}.  It must be opened in binary mode | 
					
						
							|  |  |  |   (\code{'wb'} or \code{'w+b'}). | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1996-06-26 20:20:57 +00:00
										 |  |  |   If the value has (or contains an object that has) an unsupported type, | 
					
						
							| 
									
										
										
										
											1998-03-08 06:28:00 +00:00
										 |  |  |   a \exception{ValueError} exception is raised --- but garbage data | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   will also be written to the file.  The object will not be properly | 
					
						
							|  |  |  |   read back by \function{load()}. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{load}{file} | 
					
						
							|  |  |  |   Read one value from the open file and return it.  If no valid value | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   is read, raise \exception{EOFError}, \exception{ValueError} or | 
					
						
							| 
									
										
										
										
											2000-04-03 20:13:55 +00:00
										 |  |  |   \exception{TypeError}.  The file must be an open file object opened | 
					
						
							|  |  |  |   in binary mode (\code{'rb'} or \code{'r+b'}). | 
					
						
							| 
									
										
										
										
											1996-06-26 20:20:57 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											1998-03-08 06:28:00 +00:00
										 |  |  |   \strong{Warning:} If an object containing an unsupported type was | 
					
						
							|  |  |  |   marshalled with \function{dump()}, \function{load()} will substitute | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   \code{None} for the unmarshallable type. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{dumps}{value} | 
					
						
							|  |  |  |   Return the string that would be written to a file by | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   \code{dump(\var{value}, \var{file})}.  The value must be a supported | 
					
						
							|  |  |  |   type.  Raise a \exception{ValueError} exception if value has (or | 
					
						
							|  |  |  |   contains an object that has) an unsupported type. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | \begin{funcdesc}{loads}{string} | 
					
						
							|  |  |  |   Convert the string to a value.  If no valid value is found, raise | 
					
						
							| 
									
										
										
										
											1998-02-16 20:40:37 +00:00
										 |  |  |   \exception{EOFError}, \exception{ValueError} or | 
					
						
							|  |  |  |   \exception{TypeError}.  Extra characters in the string are ignored. | 
					
						
							| 
									
										
										
										
											1994-01-02 01:22:07 +00:00
										 |  |  | \end{funcdesc} |