#11845: Pickle python functions
---------------------------+------------------------------------------------
Reporter: nbruin | Owner: was
Type: enhancement | Status: new
Priority: major | Milestone: sage-feature
Component: pickling | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
---------------------------+------------------------------------------------
Simon King pointed out that, although python function objects are normally
not guaranteed to be picklable, the marshal module is happy to serialize
code objects (although portability of the result is not guaranteed across
versions), see
[http://groups.google.com/group/sage-
devel/browse_thread/thread/f1a213d1cac0719c sage-devel thread]
Since sage pickles are supposed to be highly portable, we should probably
not enable the feature by default, but the feature can be extremely useful
when, for instance, distributing jobs across multiple worker nodes.
Some work is needed to work properly with closures, so having a debugged
and well-maintained interface for pickling python functions is desirable.
I have no idea whether it would be appropriate to stuff somewhere in the
sage library, so for now this ticket can serve as a repository.
------
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11845>
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.
