summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRaymond Hettinger <python@rcn.com>2008-02-07 20:10:49 (GMT)
committerRaymond Hettinger <python@rcn.com>2008-02-07 20:10:49 (GMT)
commit23bdcc92534fba74187bdf9663e68bf6e0d8706a (patch)
tree99d6375c0b8e8d9332275bcc960e957a8086e66d
parentff1f97307df50e5ff516b782cd326bc4e45fc754 (diff)
downloadcpython-23bdcc92534fba74187bdf9663e68bf6e0d8706a.zip
cpython-23bdcc92534fba74187bdf9663e68bf6e0d8706a.tar.gz
cpython-23bdcc92534fba74187bdf9663e68bf6e0d8706a.tar.bz2
Fix typo
-rw-r--r--Doc/library/decimal.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/library/decimal.rst b/Doc/library/decimal.rst
index 37d2b35..85df2bd 100644
--- a/Doc/library/decimal.rst
+++ b/Doc/library/decimal.rst
@@ -1597,13 +1597,13 @@ suggest, so we trap :const:`Inexact` to signal a need for more precision::
>>> float_to_decimal(math.pi)
Decimal("3.141592653589793115997963468544185161590576171875")
-Q. Why isn't the :func:`floatToDecimal` routine included in the module?
+Q. Why isn't the :func:`float_to_decimal` routine included in the module?
A. There is some question about whether it is advisable to mix binary and
decimal floating point. Also, its use requires some care to avoid the
representation issues associated with binary floating point::
- >>> floatToDecimal(1.1)
+ >>> float_to_decimal(1.1)
Decimal("1.100000000000000088817841970012523233890533447265625")
Q. Within a complex calculation, how can I make sure that I haven't gotten a