Skip to content

Commit 8757d0d

Browse files
committed
Shorten the introductory sentences
1 parent e9aafa3 commit 8757d0d

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

src/doc/en/developer/coding_in_python.rst

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -473,12 +473,11 @@ example:
473473
Note that the syntax in ``except`` is to list all the exceptions that
474474
are caught as a tuple, followed by an error message.
475475

476-
If you are writing new code to Sage, you soon face the problem of choosing an
477-
exception most suitable for an errorneous situation. This is often a tricky
478-
business. The following aims to guide you in choosing from the most relevant
479-
exceptions to Sage developers. A method (or a function) accepts input described
480-
in the ``INPUT`` block of :ref:`the docstring <section-docstring-function>` and
481-
returns output. You may raise
476+
A method or a function accepts input described in the ``INPUT`` block of
477+
:ref:`the docstring <section-docstring-function>` and returns output. If the
478+
input cannot be handled by the code, then it may raise an exception. The
479+
following aims to guide you in choosing from the most relevant exceptions to
480+
Sage:
482481

483482
- `TypeError <https://docs.python.org/3/library/exceptions.html#TypeError>`_:
484483
if the input belongs to a class of objects that are not supported by the

0 commit comments

Comments
 (0)