#10768: Revisit the pickle jar procedure
-------------------------------+-----------------------------
Reporter: nthiery | Owner: was
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-wishlist
Component: pickling | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+-----------------------------
Comment (by nthiery):
Hi Volker!
I don't have a good view on the order of magnitudes. Yet, with the
proposed protocol, pickles that don't change don't get duplicated between
versions, and I'd expect that only a few pickles get changed from one
version to the other (especially if we emphasize pickling by construction
rather than by internal data structure). A good experiment would be to
regenerate a new pickle jar, and see how much we have added to it since
last time!
I don't have a strong opinion about whether the pickle jar should be
maintained under git or not. If we can affor it, that makes things easier,
as changes to the pickle jar can be done within the usual workflow. But if
it's too big, it's too big.
Cheers,
Nicolas
--
Ticket URL: <http://trac.sagemath.org/ticket/10768#comment:12>
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/groups/opt_out.
