#13184: Some Homset are not unique parents
--------------------------+-------------------------------------------------
Reporter: caruso | Owner: nthiery
Type: defect | Status: new
Priority: major | Milestone: sage-5.1
Component: categories | Keywords: homset unique parent
Work issues: | Report Upstream: N/A
Reviewers: | Authors:
Merged in: | Dependencies:
Stopgaps: |
--------------------------+-------------------------------------------------
I guess it is a bug:
{{{
sage: k = GF(5)
sage: H = Hom(k,k)
sage: H2 = Hom(k,k)
sage: H is H2
False
}}}
I don't know what is the correct way to fix this problem.
More precisely, in sage.categories.homset (l. 223-227), one can read:
{{{
try:
# Apparently X._Hom_ is supposed to be cached
return X._Hom_(Y, category)
except (AttributeError, TypeError):
pass
}}}
However, in this particular case, k._Hom_ is apparently not cached. IMHO,
caching should be the job of sage.categories.homset.Hom is all cases, but
I might be wrong.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13184>
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.
