#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 |
-------------------------------------+-------------------------------------
Comment (by nthiery):
Ah, yes, that could one way to handle it. Thanks!
Sorry for the silence. I have been toying with a variant of it,
putting a similar test in the Homset constructor. I don't know which
one is best. Yours is more local context-wise (it only affects
modules); mine is more local code wise.
However while doing this I stumbled on another issue, which is that
now {{{X in category}}} is not necessarily equivalent to
{{{X.category().is_subcategory(category)}}}. This is ok theoretically,
but there is at least one spot in the code, namely in Hom, where this
has to be fixed, which in turn opens a can of pickling worms.
Hopefully I'll have a proposal later tonight.
Cheers,
Nicolas
--
Ticket URL: <http://trac.sagemath.org/ticket/15801#comment:36>
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.
