#13835: pickle_function, unpickle_function don't handle default arguments
properly
----------------------------+-----------------------------------------------
Reporter: cnassau | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-5.6
Component: pickling | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------+-----------------------------------------------
Comment (by nbruin):
Perhaps #11845 has some relevant information?
Furthermore: Don't do this as a way to make sage objects "picklable". The
python marshal module does allow for serialization of code objects but one
should not consider the resulting serializations as a "pickle". The level
to which pickles are meant to be backward/forward compatible simply cannot
be guaranteed for code objects.
If your object's state consists in an essential way on a code object: too
bad, your object is not pickle-able in the normal sense of the word. You
are depending on state that is only available in a python-version
dependent form and that's not good enough for Pickle.
(for instance, if sage were to move to Python 3, your pickle would have to
break)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13835#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
