#15801: Categories over a base ring category
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: categories | Resolution:
Keywords: | Merged in:
Authors: Nicolas M. Thiéry | Reviewers: Travis Scrimshaw
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/categories/over-a-base- | 2114d54f98b80c9542b61051600d9ff686f99f13
ring-category-15801 | Stopgaps:
Dependencies: #10963, #16275 |
-------------------------------------+-------------------------------------
Comment (by nthiery):
Replying to [comment:38 tscrim]:
> I think we should leave my `_Hom_` hack in because the homset is a
module (when the codomain is a module as well) and at least we're somewhat
demonstrating that when specifying that the homset has a base ring
(through the `Parent.__init__`). So I'd say my `_Hom_` and #16275 should
coexist in the final version.
Sorry, I was unclear. Yes, we definitely need some Hom hack to setup
base_ring properly by passing it to __init__. My question is just whether
this hack belongs to a custom {{{_Hom_}}} method as you did or to
{{{Homset.__init__}}} as in my (yet unpushed) branch.
--
Ticket URL: <http://trac.sagemath.org/ticket/15801#comment:39>
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.
