Ticket #12876: trac_12876-reviewer.patch

sage/categories/hecke_modules.py

@@ -100 +100 @@
             The sole purpose of this method is to construct the homset
             as a :class:`~sage.modular.hecke.homspace.HeckeModuleHomspace`. If
             ``category`` is specified and is not a subcategory of
-            :class:`HeckeModules`(), a ``TypeError`` is raised instead
+            :class:`HeckeModules`, a ``TypeError`` is raised instead
 
             This method is not meant to be called directly. Please use
             :func:`sage.categories.homset.Hom` instead.
@@ -114 +114 @@
                 <class 'sage.modular.hecke.homspace.HeckeModuleHomspace_with_category'>
                 sage: TestSuite(H).run(skip=["_test_zero", "_test_elements"])
 
-            Fixing :meth:'_test_zero' (``__call__`` should accept a
+            Fixing :meth:`_test_zero` (``__call__`` should accept a
             function as input) and :meth:`_test_elements` (modular
             form morphisms elements should inherit from categories) is
-            :trac:'???'.
+            :trac:`???`.
 
             TESTS::
 

sage/categories/homset.py

@@ -153 +153 @@
         TypeError: Integer Ring is not in Category of groups
 
     A parent may specify how to construct certain homsets by
-    implementing a method :meth:`_Hom_`(codomain, category). This
+    implementing a method ``_Hom_(self, codomain, category)``. This
     method should either construct the requested homset or raise a
     ``TypeError``. This hook is currently mostly used to create
     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
     equal to, but not identic with, the given (co)domain.
 
-    By :trac:`9138`, we abandon the uniqueness of hom sets, if the domain or
+    By :trac:`9138`, we abandon the uniqueness of homsets, if the domain or
     codomain break uniqueness::
 
         sage: from sage.rings.polynomial.multi_polynomial_ring import MPolynomialRing_polydict_domain
@@ -230 +230 @@
         sage: Hom(PA,PJ, Rngs())
         Set of Morphisms from <type 'sage.structure.parent.Parent'> to <type 'sage.structure.parent.Parent'> in Category of rngs
 
-    TODO: design decision: how much of the homset comes from the
-    category of X and Y, and how much from the specific X and Y.  In
-    particular, do we need several parent classes depending on X and
-    Y, or does the difference only lie in the elements (i.e. the
-    morphism), and of course how the parent calls their constructors.
+    ..TODO::
+
+        design decision: how much of the homset comes from the
+        category of `X` and `Y`, and how much from the specific `X` and `Y`.  In
+        particular, do we need several parent classes depending on `X` and
+        `Y`, or does the difference only lie in the elements (i.e. the
+        morphism), and of course how the parent calls their constructors.
 
     TESTS::
 

sage/categories/rings.py

@@ -105 +105 @@
             The sole purpose of this method is to construct the homset
             as a :class:`~sage.rings.homset.RingHomset`. If
             ``category`` is specified and is not a subcategory of
-            :class:`Rings`(), a ``TypeError`` is raised instead
+            :class:`Rings`, a ``TypeError`` is raised instead
 
             This method is not meant to be called directly. Please use
             :func:`sage.categories.homset.Hom` instead.
@@ -151 +151 @@
             rings also inherits from the base class of
             rings. Therefore, we implemented a ``__mul__``
             method for parents, that calls a ``_mul_``
-            method implemented here. See trac ticket #11068.
+            method implemented here. See :trac:`11068`.
 
             INPUT:
 
@@ -233 +233 @@
             The code is copied from the base class of rings.
             This is since there are rings that do not inherit
             from that class, such as matrix algebras.  See
-            trac ticket #11068.
+            :trac:`11068`.
 
             EXAMPLE::
 
@@ -269 +269 @@
             :class:`~sage.rings.ring.Ring`. This is
             because there are rings that do not inherit
             from that class, such as matrix algebras.
-            See trac ticket #11068.
+            See :trac:`11068`.
 
             INPUT:
 
@@ -473 +473 @@
 
             ``MS`` is not an instance of :class:`~sage.rings.ring.Ring`.
             But since its category was fully initalised (which is not
-            by default, by trac ticket #11900), it is an instance of
+            by default, by :trac:`11900`), it is an instance of
             the parent class of the category of rings. The quotient
             method is inherited from there::
 

sage/structure/parent.pyx

@@ -1515 +1515 @@
             Set of Morphisms from Rational Field to Integer Ring in Category of sets
 
         A parent may specify how to construct certain homsets by
-        implementing a method :meth:`_Hom_`(codomain, category).
+        implementing a method ``_Hom_(self, codomain, category)``.
         See :func:`~sage.categories.homset.Hom` for details.
         """
         from sage.categories.homset import Hom