#10768: Revisit the pickle jar procedure
-------------------------------+--------------------------------------------
Reporter: nthiery | Owner: was
Type: enhancement | Status: new
Priority: major | Milestone: sage-wishlist
Component: pickling | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by andrew.mathas):
Hi Nicolas,
I want to add to your proposal that the pickle_jar be properly documented.
As far as I am aware, there is currently no documentation on what the
pickle jar is for, how it should be used, and what to do when a pickle
breaks with
{{{
sage -t devel/sage-sf/sage/structure/sage_object.pyx
}}}
for example. A non-trivial example for using `register_unpickle_override`
should also be added.
Secondly, I think that the procedure for adding new pickles to the jar
needs to streamlined. Again, I don't believe that it is described anywhere
when or how this happens, but I do know that there are many "new" classes
which are not represented in the pickle_jar with the consequence that the
pickle_jar is unable to check backward compatibility for these classes.
Andrew
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10768#comment:10>
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.
