#15692: Value of cached methods should not always be pickled
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: pickling | Resolution:
Keywords: pickling hash | Merged in:
cache | Reviewers: Vincent Delecroix
Authors: Julian Rueth | Work issues:
Report Upstream: N/A | Commit:
Branch: | 67c7782df66179ebc0e7dd09b2518f76b6ecf198
u/saraedum/ticket/15692 | Stopgaps:
Dependencies: #16337 |
-------------------------------------+-------------------------------------
Comment (by novoselt):
Replying to [comment:30 jdemeyer]:
> What's the use case for `pickle=True`? I would say that a cache should
''never'' be pickled.
If something in cache is expensive to compute and you want to dump your
object so that later you can load it with cache full. I use it regularly
for my personal classes and some time ago it was also used for lists of
reflexive polytopes (to store points and faces that were taking many
seconds to recompute). One may argue whether it is the best way
philosophically or not, but it is easy and it works, so it is nice to have
this possibility available.
--
Ticket URL: <http://trac.sagemath.org/ticket/15692#comment:31>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
