#715: Parents probably not reclaimed due to too much caching
----------------------------+-----------------------------------------------
Reporter: robertwb | Owner: somebody
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords: weak cache coercion
Work_issues: fix doctests | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #9138, #11900
----------------------------+-----------------------------------------------
Comment(by SimonKing):
Hi Volker,
good that you managed to install it. Meanwhile I think I can debug it
without the core dump - I think mistaking a sparse with a dense vector
space is a pretty convincing reason for a segfault.
However, I hate that old code!!
I tried `verify_action`, but then hundreds of tests fail in
sage/modular/modsym/space.py. So, apparently it is very common to have
non-unique parents in such a way that the action can ''not'' be fixed!
For example, I see errors like
{{{
TypeError: Coercion of [Infinity] - [0] (of type <class
'sage.modular.modsym.boundary.BoundarySpaceElement'>) into Space of
Boundary Modular Symbols for Congruence Subgroup Gamma0(43) of weight 2
and over Rational Field not (yet) defined.
}}}
Anyway, `verify_action` is no solution.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:58>
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.
