Message156069
When pickling a function object, if it cannot be saved as a global the C implementation falls back to using copyreg/__reduce__/__reduce_ex__.
The comment for the changeset which added this fallback claims that it is for compatibility with the Python implementation. See
http://hg.python.org/cpython/rev/c6753db9c6af
However, the current python implementations do not have any such fallback.
This affects both 2.x and 3.x.
For example
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import pickle, cPickle, copy_reg
>>> def f():
... pass
...
>>> _f = f
>>> del f
>>> copy_reg.pickle(type(_f), lambda obj: (str, ("FALLBACK",)))
>>> cPickle.dumps(_f)
"c__builtin__\nstr\np1\n(S'FALLBACK'\np2\ntp3\nRp4\n."
>>> pickle.dumps(_f)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "c:\Python27\lib\pickle.py", line 1374, in dumps
Pickler(file, protocol).dump(obj)
File "c:\Python27\lib\pickle.py", line 224, in dump
self.save(obj)
File "c:\Python27\lib\pickle.py", line 286, in save
f(self, obj) # Call unbound method with explicit self
File "c:\Python27\lib\pickle.py", line 748, in save_global
(obj, module, name))
pickle.PicklingError: Can't pickle <function f at 0x0299A470>: it's not found as __main__.f
I don't know what should be done. I would be tempted to always fall back to copyreg/__reduce__/__reduce_ex__ when save_global fails (not just for function objects) but that might make error messages less helpful. |
|
Date |
User |
Action |
Args |
2012-03-16 19:03:39 | sbt | set | recipients:
+ sbt |
2012-03-16 19:03:39 | sbt | set | messageid: <1331924619.34.0.890923032137.issue14336@psf.upfronthosting.co.za> |
2012-03-16 19:03:38 | sbt | link | issue14336 messages |
2012-03-16 19:03:37 | sbt | create | |
|