summaryrefslogtreecommitdiffstats
path: root/Objects/floatobject.c
diff options
context:
space:
mode:
authorMartin Panter <vadmium+py@gmail.com>2016-05-08 13:45:55 (GMT)
committerMartin Panter <vadmium+py@gmail.com>2016-05-08 13:45:55 (GMT)
commit4f23cabc16027f0b6474ac8c0c1782ec5605e63b (patch)
tree8df6bff62fc3979049d5bcacead5330313305321 /Objects/floatobject.c
parentf2f1c57b7e4dcd418c278dd45161a5de65bc05d3 (diff)
downloadcpython-4f23cabc16027f0b6474ac8c0c1782ec5605e63b.zip
cpython-4f23cabc16027f0b6474ac8c0c1782ec5605e63b.tar.gz
cpython-4f23cabc16027f0b6474ac8c0c1782ec5605e63b.tar.bz2
Corrections for a/an in code comments and documentation
Diffstat (limited to 'Objects/floatobject.c')
-rw-r--r--Objects/floatobject.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/Objects/floatobject.c b/Objects/floatobject.c
index 82f9960..82cb28d 100644
--- a/Objects/floatobject.c
+++ b/Objects/floatobject.c
@@ -407,7 +407,7 @@ float_str(PyFloatObject *v)
* may lose info from fractional bits. Converting the integer to a double
* also has two failure modes: (1) a long int may trigger overflow (too
* large to fit in the dynamic range of a C double); (2) even a C long may have
- * more bits than fit in a C double (e.g., on a a 64-bit box long may have
+ * more bits than fit in a C double (e.g., on a 64-bit box long may have
* 63 bits of precision, but a C double probably has only 53), and then
* we can falsely claim equality when low-order integer bits are lost by
* coercion to double. So this part is painful too.