#18066: Cleanup of ModulesWithBasis and friends
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: tscrim
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.10
Component: categories | Resolution:
Keywords: | Merged in:
Authors: Travis Scrimshaw | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/categories/cleanup_CFM_modules_wBasis-18066|
954e3542ccc00ef3cc294f19019da3608d87a5a8
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nthiery):
Replying to [comment:2 tscrim]:
> Also a question mostly for Nicolas, do we still need
`_apply_module_morphism`? Is it just a method so that we don't have to
create a full morphism object?
As far as I know, that was indeed the motivation when Mike H implemented
it. I imagine it can make sense in certain cases where many different
morphisms are applied. But I don't have a strong opinion either.
--
Ticket URL: <http://trac.sagemath.org/ticket/18066#comment:8>
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.
