You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

202 lines
7.3 KiB

4 years ago
  1. # THIS FILE GENERATED FROM SETUP.PY
  2. this_version = '0.2.8.2'
  3. stable_version = '0.2.8.2'
  4. readme = '''-----------------------------
  5. dill: serialize all of python
  6. -----------------------------
  7. About Dill
  8. ==========
  9. ``dill`` extends python's ``pickle`` module for serializing and de-serializing
  10. python objects to the majority of the built-in python types. Serialization
  11. is the process of converting an object to a byte stream, and the inverse
  12. of which is converting a byte stream back to on python object hierarchy.
  13. ``dill`` provides the user the same interface as the ``pickle`` module, and
  14. also includes some additional features. In addition to pickling python
  15. objects, ``dill`` provides the ability to save the state of an interpreter
  16. session in a single command. Hence, it would be feasable to save a
  17. interpreter session, close the interpreter, ship the pickled file to
  18. another computer, open a new interpreter, unpickle the session and
  19. thus continue from the 'saved' state of the original interpreter
  20. session.
  21. ``dill`` can be used to store python objects to a file, but the primary
  22. usage is to send python objects across the network as a byte stream.
  23. ``dill`` is quite flexible, and allows arbitrary user defined classes
  24. and functions to be serialized. Thus ``dill`` is not intended to be
  25. secure against erroneously or maliciously constructed data. It is
  26. left to the user to decide whether the data they unpickle is from
  27. a trustworthy source.
  28. ``dill`` is part of ``pathos``, a python framework for heterogeneous computing.
  29. ``dill`` is in active development, so any user feedback, bug reports, comments,
  30. or suggestions are highly appreciated. A list of known issues is maintained
  31. at http://trac.mystic.cacr.caltech.edu/project/pathos/query.html, with a public
  32. ticket list at https://github.com/uqfoundation/dill/issues.
  33. Major Features
  34. ==============
  35. ``dill`` can pickle the following standard types:
  36. - none, type, bool, int, long, float, complex, str, unicode,
  37. - tuple, list, dict, file, buffer, builtin,
  38. - both old and new style classes,
  39. - instances of old and new style classes,
  40. - set, frozenset, array, functions, exceptions
  41. ``dill`` can also pickle more 'exotic' standard types:
  42. - functions with yields, nested functions, lambdas,
  43. - cell, method, unboundmethod, module, code, methodwrapper,
  44. - dictproxy, methoddescriptor, getsetdescriptor, memberdescriptor,
  45. - wrapperdescriptor, xrange, slice,
  46. - notimplemented, ellipsis, quit
  47. ``dill`` cannot yet pickle these standard types:
  48. - frame, generator, traceback
  49. ``dill`` also provides the capability to:
  50. - save and load python interpreter sessions
  51. - save and extract the source code from functions and classes
  52. - interactively diagnose pickling errors
  53. Current Release
  54. ===============
  55. This documentation is for version ``dill-0.2.8.2``.
  56. The latest released version of ``dill`` is available from:
  57. https://pypi.org/project/dill
  58. ``dill`` is distributed under a 3-clause BSD license.
  59. >>> import dill
  60. >>> print (dill.license())
  61. Development Version
  62. ===================
  63. You can get the latest development version with all the shiny new features at:
  64. https://github.com/uqfoundation
  65. If you have a new contribution, please submit a pull request.
  66. Installation
  67. ============
  68. ``dill`` is packaged to install from source, so you must
  69. download the tarball, unzip, and run the installer::
  70. [download]
  71. $ tar -xvzf dill-0.2.8.2.tar.gz
  72. $ cd dill-0.2.8.2
  73. $ python setup py build
  74. $ python setup py install
  75. You will be warned of any missing dependencies and/or settings
  76. after you run the "build" step above.
  77. Alternately, ``dill`` can be installed with ``pip`` or ``easy_install``::
  78. $ pip install dill
  79. Requirements
  80. ============
  81. ``dill`` requires:
  82. - ``python``, **version >= 2.5** or **version >= 3.1**, or ``pypy``
  83. - ``pyreadline``, **version >= 1.7.1** (on windows)
  84. Optional requirements:
  85. - ``setuptools``, **version >= 0.6**
  86. - ``objgraph``, **version >= 1.7.2**
  87. More Information
  88. ================
  89. Probably the best way to get started is to look at the documentation at
  90. http://dill.rtfd.io. Also see ``dill.tests`` for a set of scripts that
  91. demonstrate how ``dill`` can serialize different python objects. You can
  92. run the test suite with ``python -m dill.tests``. The contents of any
  93. pickle file can be examined with ``undill``. As ``dill`` conforms to
  94. the ``pickle`` interface, the examples and documentation found at
  95. http://docs.python.org/library/pickle.html also apply to ``dill``
  96. if one will ``import dill as pickle``. The source code is also generally
  97. well documented, so further questions may be resolved by inspecting the
  98. code itself. Please feel free to submit a ticket on github, or ask a
  99. question on stackoverflow (**@Mike McKerns**).
  100. If you would like to share how you use ``dill`` in your work, please send
  101. an email (to **mmckerns at uqfoundation dot org**).
  102. Citation
  103. ========
  104. If you use ``dill`` to do research that leads to publication, we ask that you
  105. acknowledge use of ``dill`` by citing the following in your publication::
  106. M.M. McKerns, L. Strand, T. Sullivan, A. Fang, M.A.G. Aivazis,
  107. "Building a framework for predictive science", Proceedings of
  108. the 10th Python in Science Conference, 2011;
  109. http://arxiv.org/pdf/1202.1056
  110. Michael McKerns and Michael Aivazis,
  111. "pathos: a framework for heterogeneous computing", 2010- ;
  112. http://trac.mystic.cacr.caltech.edu/project/pathos
  113. Please see http://trac.mystic.cacr.caltech.edu/project/pathos or
  114. http://arxiv.org/pdf/1202.1056 for further information.
  115. '''
  116. license = '''Copyright (c) 2004-2016 California Institute of Technology.
  117. Copyright (c) 2016-2018 The Uncertainty Quantification Foundation.
  118. All rights reserved.
  119. This software is available subject to the conditions and terms laid
  120. out below. By downloading and using this software you are agreeing
  121. to the following conditions.
  122. Redistribution and use in source and binary forms, with or without
  123. modification, are permitted provided that the following conditions
  124. are met::
  125. - Redistribution of source code must retain the above copyright
  126. notice, this list of conditions and the following disclaimer.
  127. - Redistribution in binary form must reproduce the above copyright
  128. notice, this list of conditions and the following disclaimer in the
  129. documentations and/or other materials provided with the distribution.
  130. - Neither the name of the California Institute of Technology nor
  131. the names of its contributors may be used to endorse or promote
  132. products derived from this software without specific prior written
  133. permission.
  134. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
  135. "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
  136. TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  137. PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
  138. CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
  139. EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
  140. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
  141. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
  142. WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
  143. OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
  144. ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  145. '''