#10667: Morphisms and Objects of Categories
---------------------------+------------------------------------------------
Reporter: SimonKing | Owner: nthiery
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: categories | Keywords: objects morphisms containment
Work_issues: doctests | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #9138, #11115
---------------------------+------------------------------------------------
Comment(by nthiery):
Replying to [comment:29 SimonKing]:
> Perhaps a related question: In sage/categories/rings.py, we have
> {{{
> #!python
> class HomCategory(HomCategory):
> class ParentMethods:
> def __new__(cls, X, Y, category):
> from sage.rings.homset import RingHomset
> return RingHomset(X, Y, category = category)
> def __getnewargs__(self):
> return (self.domain(), self.codomain(), self.category())
> }}}
>
> Wouldn't it be possible to simply have
> {{{
> #!python
> class HomCategory(HomCategory):
> class ParentMethods(RingHomset):
> pass
> }}}
> ?
Somehow both are wrong; I had just put that here to make the damn thing
work for the moment: the category really should not be dealing with the
concrete classes used to implement the Homsets. That's Hom's job at best,
but we need to design a proper protocol for this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10667#comment:31>
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.
