./wip/py-dill, Utility for serialization of python objects

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.2.4, Package name: py27-dill-0.2.4, Maintainer: kamelderouiche

Required to run:
[devel/py-setuptools] [devel/readline] [lang/python27]

Required to build:

Master sites:

SHA1: f36c57e0146b9c570db7040f1a1b0da9b69a4b41
RMD160: 6a29a4e66ad8b37881ef3c02b6c02829cb05716f
Filesize: 57.233 KB

Version history: (Expand)

CVS history: (Expand)

   2014-06-09 23:12:57 by Kamel Derouiche | Files touched by this commit (5)
Log message:
Import py27-dill-0.2.1 as wip/py-dill.

Dill extends python's 'pickle' module for serializing and de-serializing
python objects to the majority of the built-in python types. Serialization
is the process of converting an object to a byte stream, and the inverse
of which is converting a byte stream back to on python object hierarchy.

Dill provides the user the same interface as the 'pickle' module, and
also includes some additional features. In addition to pickling python
objects, dill provides the ability to save the state of an interpreter
session in a single command.  Hence, it would be feasable to save a
interpreter session, close the interpreter, ship the pickled file to
another computer, open a new interpreter, unpickle the session and
thus continue from the 'saved' state of the original interpreter

Dill can be used to store python objects to a file, but the primary
usage is to send python objects across the network as a byte stream.
Dill is quite flexible, and allows arbitrary user defined classes
and funcitons to be serialized.  Thus dill is not intended to be
secure against erroneously or maliciously constructed data. It is
left to the user to decide whether the data they unpickle is from
a trustworthy source.