| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 1 |  | 
 | 2 | :mod:`marshal` --- Internal Python object serialization | 
 | 3 | ======================================================= | 
 | 4 |  | 
 | 5 | .. module:: marshal | 
 | 6 |    :synopsis: Convert Python objects to streams of bytes and back (with different | 
 | 7 |               constraints). | 
 | 8 |  | 
 | 9 |  | 
 | 10 | This module contains functions that can read and write Python values in a binary | 
 | 11 | format.  The format is specific to Python, but independent of machine | 
 | 12 | architecture issues (e.g., you can write a Python value to a file on a PC, | 
 | 13 | transport the file to a Sun, and read it back there).  Details of the format are | 
 | 14 | undocumented on purpose; it may change between Python versions (although it | 
 | 15 | rarely does). [#]_ | 
 | 16 |  | 
 | 17 | .. index:: | 
 | 18 |    module: pickle | 
 | 19 |    module: shelve | 
 | 20 |    object: code | 
 | 21 |  | 
 | 22 | This is not a general "persistence" module.  For general persistence and | 
 | 23 | transfer of Python objects through RPC calls, see the modules :mod:`pickle` and | 
 | 24 | :mod:`shelve`.  The :mod:`marshal` module exists mainly to support reading and | 
 | 25 | writing the "pseudo-compiled" code for Python modules of :file:`.pyc` files. | 
 | 26 | Therefore, the Python maintainers reserve the right to modify the marshal format | 
 | 27 | in backward incompatible ways should the need arise.  If you're serializing and | 
 | 28 | de-serializing Python objects, use the :mod:`pickle` module instead. | 
 | 29 |  | 
 | 30 | .. warning:: | 
 | 31 |  | 
 | 32 |    The :mod:`marshal` module is not intended to be secure against erroneous or | 
 | 33 |    maliciously constructed data.  Never unmarshal data received from an | 
 | 34 |    untrusted or unauthenticated source. | 
 | 35 |  | 
 | 36 | Not all Python object types are supported; in general, only objects whose value | 
 | 37 | is independent from a particular invocation of Python can be written and read by | 
 | 38 | this module.  The following types are supported: ``None``, integers, long | 
 | 39 | integers, floating point numbers, strings, Unicode objects, tuples, lists, | 
 | 40 | dictionaries, and code objects, where it should be understood that tuples, lists | 
 | 41 | and dictionaries are only supported as long as the values contained therein are | 
 | 42 | themselves supported; and recursive lists and dictionaries should not be written | 
 | 43 | (they will cause infinite loops). | 
 | 44 |  | 
| Guido van Rossum | da27fd2 | 2007-08-17 00:24:54 +0000 | [diff] [blame] | 45 | .. warning:: | 
 | 46 |     | 
 | 47 |    On machines where C's ``long int`` type has more than 32 bits (such as the | 
 | 48 |    DEC Alpha), it is possible to create plain Python integers that are longer | 
 | 49 |    than 32 bits. If such an integer is marshaled and read back in on a machine | 
 | 50 |    where C's ``long int`` type has only 32 bits, a Python long integer object | 
 | 51 |    is returned instead.  While of a different type, the numeric value is the | 
 | 52 |    same.  (This behavior is new in Python 2.2.  In earlier versions, all but the | 
 | 53 |    least-significant 32 bits of the value were lost, and a warning message was | 
 | 54 |    printed.) | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 55 |  | 
 | 56 | There are functions that read/write files as well as functions operating on | 
 | 57 | strings. | 
 | 58 |  | 
 | 59 | The module defines these functions: | 
 | 60 |  | 
 | 61 |  | 
 | 62 | .. function:: dump(value, file[, version]) | 
 | 63 |  | 
 | 64 |    Write the value on the open file.  The value must be a supported type.  The | 
 | 65 |    file must be an open file object such as ``sys.stdout`` or returned by | 
 | 66 |    :func:`open` or :func:`os.popen`.  It must be opened in binary mode (``'wb'`` | 
 | 67 |    or ``'w+b'``). | 
 | 68 |  | 
 | 69 |    If the value has (or contains an object that has) an unsupported type, a | 
 | 70 |    :exc:`ValueError` exception is raised --- but garbage data will also be written | 
 | 71 |    to the file.  The object will not be properly read back by :func:`load`. | 
 | 72 |  | 
 | 73 |    .. versionadded:: 2.4 | 
 | 74 |       The *version* argument indicates the data format that ``dump`` should use | 
 | 75 |       (see below). | 
 | 76 |  | 
 | 77 |  | 
 | 78 | .. function:: load(file) | 
 | 79 |  | 
 | 80 |    Read one value from the open file and return it.  If no valid value is read | 
 | 81 |    (e.g. because the data has a different Python version's incompatible marshal | 
 | 82 |    format), raise :exc:`EOFError`, :exc:`ValueError` or :exc:`TypeError`.  The | 
 | 83 |    file must be an open file object opened in binary mode (``'rb'`` or | 
 | 84 |    ``'r+b'``). | 
 | 85 |  | 
 | 86 |    .. warning:: | 
 | 87 |  | 
 | 88 |       If an object containing an unsupported type was marshalled with :func:`dump`, | 
 | 89 |       :func:`load` will substitute ``None`` for the unmarshallable type. | 
 | 90 |  | 
 | 91 |  | 
 | 92 | .. function:: dumps(value[, version]) | 
 | 93 |  | 
 | 94 |    Return the string that would be written to a file by ``dump(value, file)``.  The | 
 | 95 |    value must be a supported type.  Raise a :exc:`ValueError` exception if value | 
 | 96 |    has (or contains an object that has) an unsupported type. | 
 | 97 |  | 
 | 98 |    .. versionadded:: 2.4 | 
 | 99 |       The *version* argument indicates the data format that ``dumps`` should use | 
 | 100 |       (see below). | 
 | 101 |  | 
 | 102 |  | 
 | 103 | .. function:: loads(string) | 
 | 104 |  | 
 | 105 |    Convert the string to a value.  If no valid value is found, raise | 
 | 106 |    :exc:`EOFError`, :exc:`ValueError` or :exc:`TypeError`.  Extra characters in the | 
 | 107 |    string are ignored. | 
 | 108 |  | 
 | 109 |  | 
 | 110 | In addition, the following constants are defined: | 
 | 111 |  | 
 | 112 | .. data:: version | 
 | 113 |  | 
 | 114 |    Indicates the format that the module uses. Version 0 is the historical format, | 
 | 115 |    version 1 (added in Python 2.4) shares interned strings and version 2 (added in | 
 | 116 |    Python 2.5) uses a binary format for floating point numbers. The current version | 
 | 117 |    is 2. | 
 | 118 |  | 
 | 119 |    .. versionadded:: 2.4 | 
 | 120 |  | 
 | 121 |  | 
 | 122 | .. rubric:: Footnotes | 
 | 123 |  | 
 | 124 | .. [#] The name of this module stems from a bit of terminology used by the designers of | 
 | 125 |    Modula-3 (amongst others), who use the term "marshalling" for shipping of data | 
 | 126 |    around in a self-contained form. Strictly speaking, "to marshal" means to | 
 | 127 |    convert some data from internal to external form (in an RPC buffer for instance) | 
 | 128 |    and "unmarshalling" for the reverse process. | 
 | 129 |  |