#15692: Value of cached methods should not always be pickled
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: needs_info
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: | b2aa4073a6724e0c92c719f8d3eb232ef0bc2102
u/saraedum/ticket/15692 | Stopgaps:
Dependencies: #16337 |
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:19 saraedum]:
> Replying to [comment:16 vdelecroix]:
> > I think that disabling the cache by default on pickle is a good
improvement. However, the class `ClearCacheOnPickle` that you remove in
your branch had several purposes: clear the cache on pickle but also on
copy. Your version keep the cache on copy and that might not be
appropriate for classes that used `ClearCacheOnPickle`.
> Thanks for pointing this out. What should we do about this? Should
caches ever be copied actually?
I guess not. And if you really want to, it is always possible to fill the
cache manually.
--
Ticket URL: <http://trac.sagemath.org/ticket/15692#comment:21>
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.
