| Georg Brandl | 0eaab97 | 2009-06-08 08:00:22 +0000 | [diff] [blame] | 1 | :mod:`pickletools` --- Tools for pickle developers | 
 | 2 | ================================================== | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 3 |  | 
 | 4 | .. module:: pickletools | 
| Georg Brandl | 1824415 | 2009-09-02 20:34:52 +0000 | [diff] [blame] | 5 |    :synopsis: Contains extensive comments about the pickle protocols and | 
 | 6 |               pickle-machine opcodes, as well as some useful functions. | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 7 |  | 
| Alexander Belopolsky | cc75a86 | 2011-01-13 21:58:44 +0000 | [diff] [blame] | 8 | **Source code:** :source:`Lib/pickletools.py` | 
 | 9 |  | 
 | 10 | -------------- | 
 | 11 |  | 
 | 12 |  | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 13 | This module contains various constants relating to the intimate details of the | 
| Alexandre Vassalotti | ffcec43 | 2009-04-03 06:07:29 +0000 | [diff] [blame] | 14 | :mod:`pickle` module, some lengthy comments about the implementation, and a | 
 | 15 | few useful functions for analyzing pickled data.  The contents of this module | 
 | 16 | are useful for Python core developers who are working on the :mod:`pickle`; | 
 | 17 | ordinary users of the :mod:`pickle` module probably won't find the | 
 | 18 | :mod:`pickletools` module relevant. | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 19 |  | 
| Alexander Belopolsky | cc75a86 | 2011-01-13 21:58:44 +0000 | [diff] [blame] | 20 | Command line usage | 
 | 21 | ------------------ | 
 | 22 |  | 
 | 23 | .. versionadded:: 3.2 | 
 | 24 |  | 
 | 25 | When invoked from the command line, ``python -m pickletools`` will | 
 | 26 | disassemble the contents of one or more pickle files.  Note that if | 
 | 27 | you want to see the Python object stored in the pickle rather than the | 
 | 28 | details of pickle format, you may want to use ``-m pickle`` instead. | 
 | 29 | However, when the pickle file that you want to examine comes from an | 
 | 30 | untrusted source, ``-m pickletools`` is a safer option because it does | 
 | 31 | not execute pickle bytecode. | 
 | 32 |  | 
 | 33 | For example, with a tuple ``(1, 2)`` pickled in file ``x.pickle``:: | 
 | 34 |  | 
 | 35 |     $ python -m pickle x.pickle | 
 | 36 |     (1, 2) | 
 | 37 |  | 
 | 38 |     $ python -m pickletools x.pickle | 
 | 39 |         0: \x80 PROTO      3 | 
 | 40 |         2: K    BININT1    1 | 
 | 41 |         4: K    BININT1    2 | 
 | 42 |         6: \x86 TUPLE2 | 
 | 43 |         7: q    BINPUT     0 | 
 | 44 |         9: .    STOP | 
 | 45 |     highest protocol among opcodes = 2 | 
 | 46 |  | 
 | 47 | Command line options | 
 | 48 | ^^^^^^^^^^^^^^^^^^^^ | 
 | 49 |  | 
 | 50 | .. program:: pickletools | 
 | 51 |  | 
 | 52 | .. cmdoption:: -a, --annotate | 
 | 53 |  | 
 | 54 |    Annotate each line with a short opcode description. | 
 | 55 |  | 
 | 56 | .. cmdoption:: -o, --output=<file> | 
 | 57 |  | 
 | 58 |    Name of a file where the output should be written. | 
 | 59 |  | 
 | 60 | .. cmdoption:: -l, --indentlevel=<num> | 
 | 61 |  | 
 | 62 |    The number of blanks by which to indent a new MARK level. | 
 | 63 |  | 
 | 64 | .. cmdoption:: -m, --memo | 
 | 65 |  | 
 | 66 |    When multiple objects are disassembled, preserve memo between | 
 | 67 |    disassemblies. | 
 | 68 |  | 
 | 69 | .. cmdoption:: -p, --preamble=<preamble> | 
 | 70 |  | 
 | 71 |    When more than one pickle file are specified, print given preamble | 
 | 72 |    before each disassembly. | 
 | 73 |  | 
 | 74 |  | 
 | 75 |  | 
 | 76 | Programmatic Interface | 
 | 77 | ---------------------- | 
 | 78 |  | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 79 |  | 
| Alexander Belopolsky | 929d384 | 2010-07-17 15:51:21 +0000 | [diff] [blame] | 80 | .. function:: dis(pickle, out=None, memo=None, indentlevel=4, annotate=0) | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 81 |  | 
| Alexander Belopolsky | 929d384 | 2010-07-17 15:51:21 +0000 | [diff] [blame] | 82 |    Outputs a symbolic disassembly of the pickle to the file-like | 
 | 83 |    object *out*, defaulting to ``sys.stdout``.  *pickle* can be a | 
 | 84 |    string or a file-like object.  *memo* can be a Python dictionary | 
 | 85 |    that will be used as the pickle's memo; it can be used to perform | 
 | 86 |    disassemblies across multiple pickles created by the same | 
 | 87 |    pickler. Successive levels, indicated by ``MARK`` opcodes in the | 
 | 88 |    stream, are indented by *indentlevel* spaces.  If a nonzero value | 
 | 89 |    is given to *annotate*, each opcode in the output is annotated with | 
 | 90 |    a short description.  The value of *annotate* is used as a hint for | 
 | 91 |    the column where annotation should start. | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 92 |  | 
| Georg Brandl | 67b21b7 | 2010-08-17 15:07:14 +0000 | [diff] [blame] | 93 |   .. versionadded:: 3.2 | 
 | 94 |      The *annotate* argument. | 
| Alexander Belopolsky | f39f628 | 2010-07-26 18:27:49 +0000 | [diff] [blame] | 95 |  | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 96 | .. function:: genops(pickle) | 
 | 97 |  | 
| Georg Brandl | 9afde1c | 2007-11-01 20:32:30 +0000 | [diff] [blame] | 98 |    Provides an :term:`iterator` over all of the opcodes in a pickle, returning a | 
 | 99 |    sequence of ``(opcode, arg, pos)`` triples.  *opcode* is an instance of an | 
 | 100 |    :class:`OpcodeInfo` class; *arg* is the decoded value, as a Python object, of | 
 | 101 |    the opcode's argument; *pos* is the position at which this opcode is located. | 
| Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 102 |    *pickle* can be a string or a file-like object. | 
 | 103 |  | 
| Christian Heimes | 3feef61 | 2008-02-11 06:19:17 +0000 | [diff] [blame] | 104 | .. function:: optimize(picklestring) | 
 | 105 |  | 
 | 106 |    Returns a new equivalent pickle string after eliminating unused ``PUT`` | 
 | 107 |    opcodes. The optimized pickle is shorter, takes less transmission time, | 
 | 108 |    requires less storage space, and unpickles more efficiently. | 
 | 109 |  |