Opened 9 years ago
Last modified 8 years ago
#13184 closed defect
Some Homset are not unique parents — at Version 6
Reported by: | caruso | Owned by: | nthiery |
---|---|---|---|
Priority: | major | Milestone: | sage-5.10 |
Component: | categories | Keywords: | homset unique parent |
Cc: | caruso, SimonKing, nbruin | Merged in: | |
Authors: | Xavier Caruso | Reviewers: | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
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
to the sage library.
Change History (8)
Changed 9 years ago by
comment:1 Changed 9 years ago by
comment:2 Changed 9 years ago by
- Status changed from new to needs_review
comment:3 Changed 9 years ago by
- Cc caruso added
comment:4 Changed 9 years ago by
Please fill in your real name as Author.
comment:5 Changed 9 years ago by
comment:6 Changed 8 years ago by
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
I've attached a small patch fixing the problem.