# HG changeset patch
# User Simon King <simon.king@uni-jena.de>
# Date 1335535211 -7200
# Node ID 22d3e64793e13122fb576a3d888b06bd34c813c4
# Parent d70a2de8ff53f38aabbc295d55fb90e44ef9499d
#12876: Reviewer patch: Some cosmetic changes in the docs
diff --git a/sage/categories/hecke_modules.py b/sage/categories/hecke_modules.py
a
|
b
|
|
100 | 100 | The sole purpose of this method is to construct the homset |
101 | 101 | as a :class:`~sage.modular.hecke.homspace.HeckeModuleHomspace`. If |
102 | 102 | ``category`` is specified and is not a subcategory of |
103 | | :class:`HeckeModules`(), a ``TypeError`` is raised instead |
| 103 | :class:`HeckeModules`, a ``TypeError`` is raised instead |
104 | 104 | |
105 | 105 | This method is not meant to be called directly. Please use |
106 | 106 | :func:`sage.categories.homset.Hom` instead. |
… |
… |
|
114 | 114 | <class 'sage.modular.hecke.homspace.HeckeModuleHomspace_with_category'> |
115 | 115 | sage: TestSuite(H).run(skip=["_test_zero", "_test_elements"]) |
116 | 116 | |
117 | | Fixing :meth:'_test_zero' (``__call__`` should accept a |
| 117 | Fixing :meth:`_test_zero` (``__call__`` should accept a |
118 | 118 | function as input) and :meth:`_test_elements` (modular |
119 | 119 | form morphisms elements should inherit from categories) is |
120 | | :trac:'???'. |
| 120 | :trac:`???`. |
121 | 121 | |
122 | 122 | TESTS:: |
123 | 123 | |
diff --git a/sage/categories/homset.py b/sage/categories/homset.py
a
|
b
|
|
153 | 153 | TypeError: Integer Ring is not in Category of groups |
154 | 154 | |
155 | 155 | A parent may specify how to construct certain homsets by |
156 | | implementing a method :meth:`_Hom_`(codomain, category). This |
| 156 | implementing a method ``_Hom_(self, codomain, category)``. This |
157 | 157 | method should either construct the requested homset or raise a |
158 | 158 | ``TypeError``. This hook is currently mostly used to create |
159 | 159 | homsets in some specific subclass of :class:`Homset` |
… |
… |
|
177 | 177 | That's to say, the hom set found in the cache will have a (co)domain that is |
178 | 178 | equal to, but not identic with, the given (co)domain. |
179 | 179 | |
180 | | By :trac:`9138`, we abandon the uniqueness of hom sets, if the domain or |
| 180 | By :trac:`9138`, we abandon the uniqueness of homsets, if the domain or |
181 | 181 | codomain break uniqueness:: |
182 | 182 | |
183 | 183 | sage: from sage.rings.polynomial.multi_polynomial_ring import MPolynomialRing_polydict_domain |
… |
… |
|
230 | 230 | sage: Hom(PA,PJ, Rngs()) |
231 | 231 | Set of Morphisms from <type 'sage.structure.parent.Parent'> to <type 'sage.structure.parent.Parent'> in Category of rngs |
232 | 232 | |
233 | | TODO: design decision: how much of the homset comes from the |
234 | | category of X and Y, and how much from the specific X and Y. In |
235 | | particular, do we need several parent classes depending on X and |
236 | | Y, or does the difference only lie in the elements (i.e. the |
237 | | morphism), and of course how the parent calls their constructors. |
| 233 | ..TODO:: |
| 234 | |
| 235 | design decision: how much of the homset comes from the |
| 236 | category of `X` and `Y`, and how much from the specific `X` and `Y`. In |
| 237 | particular, do we need several parent classes depending on `X` and |
| 238 | `Y`, or does the difference only lie in the elements (i.e. the |
| 239 | morphism), and of course how the parent calls their constructors. |
238 | 240 | |
239 | 241 | TESTS:: |
240 | 242 | |
diff --git a/sage/categories/rings.py b/sage/categories/rings.py
a
|
b
|
|
105 | 105 | The sole purpose of this method is to construct the homset |
106 | 106 | as a :class:`~sage.rings.homset.RingHomset`. If |
107 | 107 | ``category`` is specified and is not a subcategory of |
108 | | :class:`Rings`(), a ``TypeError`` is raised instead |
| 108 | :class:`Rings`, a ``TypeError`` is raised instead |
109 | 109 | |
110 | 110 | This method is not meant to be called directly. Please use |
111 | 111 | :func:`sage.categories.homset.Hom` instead. |
… |
… |
|
151 | 151 | rings also inherits from the base class of |
152 | 152 | rings. Therefore, we implemented a ``__mul__`` |
153 | 153 | method for parents, that calls a ``_mul_`` |
154 | | method implemented here. See trac ticket #11068. |
| 154 | method implemented here. See :trac:`11068`. |
155 | 155 | |
156 | 156 | INPUT: |
157 | 157 | |
… |
… |
|
233 | 233 | The code is copied from the base class of rings. |
234 | 234 | This is since there are rings that do not inherit |
235 | 235 | from that class, such as matrix algebras. See |
236 | | trac ticket #11068. |
| 236 | :trac:`11068`. |
237 | 237 | |
238 | 238 | EXAMPLE:: |
239 | 239 | |
… |
… |
|
269 | 269 | :class:`~sage.rings.ring.Ring`. This is |
270 | 270 | because there are rings that do not inherit |
271 | 271 | from that class, such as matrix algebras. |
272 | | See trac ticket #11068. |
| 272 | See :trac:`11068`. |
273 | 273 | |
274 | 274 | INPUT: |
275 | 275 | |
… |
… |
|
473 | 473 | |
474 | 474 | ``MS`` is not an instance of :class:`~sage.rings.ring.Ring`. |
475 | 475 | But since its category was fully initalised (which is not |
476 | | by default, by trac ticket #11900), it is an instance of |
| 476 | by default, by :trac:`11900`), it is an instance of |
477 | 477 | the parent class of the category of rings. The quotient |
478 | 478 | method is inherited from there:: |
479 | 479 | |
diff --git a/sage/structure/parent.pyx b/sage/structure/parent.pyx
a
|
b
|
|
1515 | 1515 | Set of Morphisms from Rational Field to Integer Ring in Category of sets |
1516 | 1516 | |
1517 | 1517 | A parent may specify how to construct certain homsets by |
1518 | | implementing a method :meth:`_Hom_`(codomain, category). |
| 1518 | implementing a method ``_Hom_(self, codomain, category)``. |
1519 | 1519 | See :func:`~sage.categories.homset.Hom` for details. |
1520 | 1520 | """ |
1521 | 1521 | from sage.categories.homset import Hom |