#13991: Mitigate speed regressions in symmetric function related code due to
#12313
---------------------------------+------------------------------------------
Reporter: nbruin | Owner: sage-combinat
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.7
Component: combinatorics | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------------+------------------------------------------
Comment (by SimonKing):
Replying to [comment:8 nbruin]:
> In fact, you might try running the code in the python debugger and set a
breakpoint on `Hom` (I've never done that, but I assume it's possible).
The stackframes you're finding there might give you some indication for
what the code is trying to construct (and aparently has lost compared to
the reference case).
Why so complicated? A print statement would do as well. That's of course
the next thing I'll try, as soon as I'm done helping my son with his
homework.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13991#comment:9>
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.
