#11720: regularly refresh the pickle jar
-------------------------------+------------------------
Reporter: boothby | Owner: was
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.2
Component: pickling | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Changes (by SimonKing):
* cc: vbraun (added)
Comment:
I guess one question that needs to be addressed is: How can we keep track
of the pickle jar ''with git''? IICTC, the pickle jar is not under version
control, and being a binary file (`.tar.bz2`) it ''shouldn't'' be under
version control.
Each item in the pickle jar corresponds to a pair of files. One file is
pure text, describing the Sage version used to create the pickle, the
class whose instance is pickled, and the expected string representation of
the unpickled object. The second file is the actual pickle, `.sobj`.
Is git able to look into bzipped tar files? If this was the case, then we
could at least let git track the text files associated with the pickles.
Another question that needs to be addressed: How to post changes of the
pickle jar on a trac ticket? Shall one attach the new version of the
pickle jar, leaving a comment for the release manager asking him/her to
replace the old jar with the new jar? That's why I put Volker on Cc (Hi
Volker...).
And perhaps it would be nice to have a function that automatically creates
a new pickle in the jar. Yes, I know, there is a function that puts a
"text file"-"sobj"-pair for a given object into a given directory.
However, some manual work is currently involved to move this into
`SAGE_EXTCODE/pickle_jar/pickle_jar.tar.bz2`, and this should easily be
automated.
Concerning the topic of this trac ticket: If I understand correctly, there
is an option to automatically create a pickle jar during `sage -t`,
containing pickles for all objects that are subject to a `loads/dumps` doc
test. But perhaps this is overzealous, and in addition the result would
currently not be automatically put into the standard pickle jar.
However, this could be used as a starting point, to be modified so that
1. the resulting pickles would automatically be put into the standard
bzipped pickle jar in `SAGE_EXTCODE`
2. only ''new'' pickles will be added: If an sobj created in version 5.9
is bitwise identical with an sobj created in version 6.1, then we should
only have one copy of it in the pickle jar.
--
Ticket URL: <http://trac.sagemath.org/ticket/11720#comment:3>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
