lots of fixed tracebacks

Author: dham

doc/source/10_further_object-oriented_features.rst

@@ -327,9 +327,9 @@ be observed if we try to instantiate :class:`~example_code.groups_abc.Group`:
     In [1]: from example_code.groups_abc import Group
 
     In [2]: Group(1)
-    ---------------------------------------------------------------------------
-    TypeError                                 Traceback (most recent call last)
-    <ipython-input-2-76d67216101e> in <module>
+    --------------------------------------------------------------------------
+    TypeError                                Traceback (most recent call last)
+    Cell In [2], line 1
     ----> 1 Group(1)
 
     TypeError: Can't instantiate abstract class Group with abstract methods _validate, operation, symbol

doc/source/2_programs_in_files.rst

@@ -711,7 +711,7 @@ packages that are not already available before installing the package itself.
 
 .. warning::
 
-    Neither `dependencies` nor `requires`should list packages from the Python
+    Neither `dependencies` nor `requires` should list packages from the Python
     Standard Library. These are always available, and listing them will cause
     Pip to error.
 
@@ -769,13 +769,12 @@ it's false, then an error occurs. For example:
 
 .. code-block:: ipython3
 
-   In [1]: assert 1 == 0
-   ---------------------------------------------------------------------------
-   AssertionError                            Traceback (most recent call last)
-   <ipython-input-1-e99f91a18d62> in <module>
-   ----> 1 assert 1 == 0
+    --------------------------------------------------------------------------
+    AssertionError                           Traceback (most recent call last)
+    Cell In [1], line 1
+    ----> 1 assert 1==0
 
-   AssertionError:
+    AssertionError: 
 
 Pytest files
 ~~~~~~~~~~~~
@@ -804,6 +803,12 @@ are usually gathered in a separate tests folder. For example::
     │   └── test_fibonacci.py
     └── pyproject.toml
 
+.. only:: book
+
+    .. raw:: latex
+
+        \clearpage
+
 We can then invoke the tests from the shell:
 
 .. code-block:: console
@@ -1068,12 +1073,6 @@ already familiar with Git and GitHub then you will also need to work through
         GitHub. Then ensure that the tests pass on GitHub. For more information
         about how to do any of these, refer to :numref:`Appendix %s <git>`.
 
-.. only:: book
-
-    .. raw:: latex
-
-        \clearpage
-
 .. proof:exercise::
 
     Following :numref:`installable_packages`, create a :file:`pyproject.toml`

doc/source/3_objects.rst

@@ -41,15 +41,17 @@ we add an integer to a :ref:`string <textseq>`?
 
 .. code-block:: ipython3
 
-  In [1]: a = 1
-  In [2]: b = 'og'
-  In [3]: print(a + b)
-  ---------------------------------------------------------------------------
-  TypeError                                 Traceback (most recent call last)
-  <ipython-input-3-0ae8b1612688> in <module>
-  ----> 1 print(a + b)
-  
-  TypeError: unsupported operand type(s) for +: 'int' and 'str'
+    In [1]: a = 1
+
+    In [2]: b = 'og'
+
+    In [3]: print(a + b)
+    --------------------------------------------------------------------------
+    TypeError                                Traceback (most recent call last)
+    Cell In [3], line 1
+    ----> 1 print(a + b)
+
+    TypeError: unsupported operand type(s) for +: 'int' and 'str'
 
 In this error, Python is complaining that `+` does not make sense if
 the items being added (the :term:`operands`) are an integer and a
@@ -62,15 +64,17 @@ also in trouble:
 
 .. code-block:: ipython3
   
-  In [1]: a = {1, 2}
-  In [2]: b = {2, 3}
-  In [3]: print(a + b)
-  ---------------------------------------------------------------------------
-  TypeError                                 Traceback (most recent call last)
-  <ipython-input-3-0ae8b1612688> in <module>
-  ----> 1 print(a + b)
-
-  TypeError: unsupported operand type(s) for +: 'set' and 'set'
+    In [1]: a = {1, 2}
+
+    In [2]: b = {2, 3}
+
+    In [3]: print(a + b)
+    --------------------------------------------------------------------------
+    TypeError                                Traceback (most recent call last)
+    Cell In [3], line 1
+    ----> 1 print(a + b)
+
+    TypeError: unsupported operand type(s) for +: 'set' and 'set'
   
 Conversely we might suspect that two values can be added only if they are of the same
 type. However it is perfectly legal to add an integer and a :ref:`floating
@@ -700,9 +704,9 @@ Let's try our new addition functionality in action:
    x^3 + 2x + 2
 
    In [8]: print(1 + a)                                                                                               
-   ---------------------------------------------------------------------------
-   TypeError                                 Traceback (most recent call last)
-   <ipython-input-8-a42ff1c9a542> in <module>
+   --------------------------------------------------------------------------
+   TypeError                                Traceback (most recent call last)
+   Cell In [8], line 1
    ----> 1 print(1 + a)
    
    TypeError: unsupported operand type(s) for +: 'int' and 'Polynomial'

doc/source/4_style.rst

@@ -1000,11 +1000,22 @@ information:
     File:      ~/docs/principles_of_programming/object-oriented-programming/fibonacci/fibonacci.py
     Type:      function
 
-Finally, the same information is used in the :func:`web documentation
-<fibonacci.fibonacci.fib>`. Notice that the :term:`function signature` is not a
-part of the docstring. Python is capable of extracting the signature of the
-function and adding it into the documentation without the programmer having to
-manually add it to the docstring.
+.. only:: not book
+
+   Finally, the same information is used in the :func:`web documentation
+   <fibonacci.fibonacci.fib>`. Notice that the :term:`function signature` is
+   not a part of the docstring. Python is capable of extracting the signature
+   of the function and adding it into the documentation without the programmer
+   having to manually add it to the docstring.
+
+.. only:: book
+
+   Finally, the same information is used in the web documentation
+   of the function. Notice that the :term:`function signature` is
+   not a part of the docstring. Python is capable of extracting the signature
+   of the function and adding it into the documentation without the programmer
+   having to manually add it to the docstring.
+
 
 Where to use docstrings
 .......................

doc/source/7_inheritance.rst

@@ -595,12 +595,6 @@ than the current one with:
 Observe that since `type(self)` is a :term:`class`, we can :term:`instantiate`
 it by calling it.
 
-.. only:: book
-
-    .. raw:: latex
-
-        \clearpage
-
 Calling parent class methods
 ----------------------------
 

doc/source/conf.py

@@ -61,7 +61,7 @@
 # General information about the project.
 project = u'Object-oriented Programming'
 author = u'David A. Ham'
-copyright = u'2019-2021, David A. Ham'
+copyright = u'2019-2023, David A. Ham'
 
 mathjax_path = \
     "https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML" # noqa 501
@@ -71,7 +71,7 @@
 # built documents.
 #
 # The short X.Y version.
-version = '2021.0'
+version = '2023.0'
 # The full version, including alpha/beta/rc tags.
 release = ''
 
@@ -255,6 +255,7 @@
 \title{Object-oriented Programming}
 \subtitle{in Python for Mathematicians}
 \edition{2021}
+\edition{2023}
 \makeatletter
    \fancypagestyle{normal}{
     \fancyhf{}