summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTerry Jan Reedy <tjreedy@udel.edu>2014-09-30 23:08:02 (GMT)
committerTerry Jan Reedy <tjreedy@udel.edu>2014-09-30 23:08:02 (GMT)
commitcd09571894d8e0a872552082ee394b370f84b71c (patch)
treefae96ed159801c85f00a0a37416f5715f1ff5b08
parent5eb0645ed5dbab6f1c228a4ecce6d9949c32b119 (diff)
parentb6271f2d2b3f893ebf80f7ede85b70bd789c1efb (diff)
downloadcpython-cd09571894d8e0a872552082ee394b370f84b71c.zip
cpython-cd09571894d8e0a872552082ee394b370f84b71c.tar.gz
cpython-cd09571894d8e0a872552082ee394b370f84b71c.tar.bz2
Merge with 3.4
-rw-r--r--Doc/reference/datamodel.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/reference/datamodel.rst b/Doc/reference/datamodel.rst
index 24f3f93..0757aa8 100644
--- a/Doc/reference/datamodel.rst
+++ b/Doc/reference/datamodel.rst
@@ -222,7 +222,7 @@ Ellipsis
at the mercy of the underlying machine architecture (and C or Java
implementation) for the accepted range and handling of overflow. Python does not
support single-precision floating point numbers; the savings in processor and
- memory usage that are usually the reason for using these is dwarfed by the
+ memory usage that are usually the reason for using these are dwarfed by the
overhead of using objects in Python, so there is no reason to complicate the
language with two kinds of floating point numbers.