id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,merged,author,reviewer,upstream,work_issues,branch,commit,dependencies,stopgaps
13184,Some Homset are not unique parents,caruso,nthiery,"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.
----
Apply
1. [attachment:trac_13184_sage_5.9.beta.patch]",defect,closed,major,sage-5.10,categories,fixed,homset unique parent,caruso SimonKing nbruin,sage-5.10.beta0,"Xavier Caruso, Frédéric Chapoton",Travis Scrimshaw,N/A,,,,#14159,