Rooba
/
cpython
mirror of https://github.com/python/cpython.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Issue #19272: slight clarification of pickle docs with regard to lambda.

This commit is contained in:
Ethan Furman 2013-10-18 00:45:40 -07:00
parent 63c141cacd
commit 2498d9e968
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Doc/library/pickle.rst
View File

@ -384,7 +384,8 @@ The following types can be pickled:
* tuples, lists, sets, and dictionaries containing only picklable objects
* functions defined at the top level of a module
* functions defined at the top level of a module (using :keyword:`def`, not
:keyword:`lambda`)
* built-in functions defined at the top level of a module
@ -402,7 +403,7 @@ raised in this case. You can carefully raise this limit with
:func:`sys.setrecursionlimit`.
Note that functions (built-in and user-defined) are pickled by "fully qualified"
name reference, not by value. This means that only the function name is
name reference, not by value. [#]_ This means that only the function name is
pickled, along with the name of the module the function is defined in. Neither
the function's code, nor any of its function attributes are pickled. Thus the
defining module must be importable in the unpickling environment, and the module
@ -850,6 +851,9 @@ The following example reads the resulting pickled data. ::
.. [#] Don't confuse this with the :mod:`marshal` module
.. [#] This is why :keyword:`lambda` functions cannot be pickled: all
:keyword:`lambda` functions share the same name: ``<lambda>``.
.. [#] The exception raised will likely be an :exc:`ImportError` or an
:exc:`AttributeError` but it could be something else.