Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix formatting in typing_anti_pitch.rst #1512

Merged
merged 3 commits into from
Nov 27, 2023
Merged

Fix formatting in typing_anti_pitch.rst #1512

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e92babc
Fix formatting in typing_anti_pitch.rst
MegaIng Nov 26, 2023
11407d8
Update typing_anti_pitch.rst
MegaIng Nov 26, 2023
27383d4
Update docs/source/typing_anti_pitch.rst
hauntsaninja Nov 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/source/typing_anti_pitch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,12 @@
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.
.. code-block:: none

hauntsaninja marked this conversation as resolved.
Show resolved Hide resolved
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
Expand All @@ -19,7 +21,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
Expand Down
Loading