aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMegaIng <cornelius@krupp.hamburg>2023-11-27 02:26:04 +0100
committerGitHub <noreply@github.com>2023-11-26 17:26:04 -0800
commit0c89ed564069639d3a62ebd9790acdc182719c2f (patch)
treeb9dea1576478f975abdcb70f6aec492f6a1b6dd3
parent3f139608cb139c04ae4330b134e2556b2cf25fcd (diff)
downloadtyping-upstream-master.tar.gz
Fix formatting in typing_anti_pitch.rst (#1512)upstream-master
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
-rw-r--r--docs/source/typing_anti_pitch.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/source/typing_anti_pitch.rst b/docs/source/typing_anti_pitch.rst
index 1d2796e..fbd5676 100644
--- a/docs/source/typing_anti_pitch.rst
+++ b/docs/source/typing_anti_pitch.rst
@@ -3,10 +3,10 @@
Reasons to avoid static type checking
=====================================
-In the words of :pep:`484`::
+In the words of :pep:`484`:
- It should also be emphasized that Python will remain a dynamically typed language, and the
- authors have no desire to ever make type hints mandatory, even by convention.
+ It should also be emphasized that Python will remain a dynamically typed language, and
+ the authors have no desire to ever make type hints mandatory, even by convention.
The idea that dynamism in Python is a strength of the language is reflected in the fact that
Python's type system is gradual. See :pep:`483` for details, but the long and short of this is
@@ -19,7 +19,7 @@ On the other -- well, I love type checking, but I would quit Python if I had to
possible strictness checks that type checkers offer.
Anyway, with all that said, here's a list of possible reasons to not use static type checking
-in Python::
+in Python:
* You simply don't want to. Python is a tool that is meant to serve you. Python is a big tent,
multi-paradigm language that generally allows you to do things in the way that best suits your