iframe-proxy | Sunbelt Computer Software

556 lines (480 loc) · 17.7 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# Translators:
# Alireza Shabani (Revisto) <theRevisto@gmail.com>, 2025
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-07-25 12:59+0330\n"
"PO-Revision-Date: 2021-06-28 01:50+0000\n"
"Last-Translator: Alireza Shabani (Revisto) <theRevisto@gmail.com>, 2025\n"
"Language-Team: Persian (https://app.transifex.com/python-doc/teams/5390/"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
#: ../../tutorial/floatingpoint.rst:10
msgid "Floating-Point Arithmetic:  Issues and Limitations"
#: ../../tutorial/floatingpoint.rst:16
"Floating-point numbers are represented in computer hardware as base 2 "
"(binary) fractions.  For example, the **decimal** fraction ``0.625`` has "
"value 6/10 + 2/100 + 5/1000, and in the same way the **binary** fraction "
"``0.101`` has value 1/2 + 0/4 + 1/8. These two fractions have identical "
"values, the only real difference being that the first is written in base 10 "
"fractional notation, and the second in base 2."
#: ../../tutorial/floatingpoint.rst:23
"Unfortunately, most decimal fractions cannot be represented exactly as "
"binary fractions.  A consequence is that, in general, the decimal floating-"
"point numbers you enter are only approximated by the binary floating-point "
"numbers actually stored in the machine."
#: ../../tutorial/floatingpoint.rst:28
"The problem is easier to understand at first in base 10.  Consider the "
"fraction 1/3.  You can approximate that as a base 10 fraction::"
#: ../../tutorial/floatingpoint.rst:31
msgid "0.3"
#: ../../tutorial/floatingpoint.rst:33 ../../tutorial/floatingpoint.rst:37
msgid "or, better, ::"
#: ../../tutorial/floatingpoint.rst:35
msgid "0.33"
#: ../../tutorial/floatingpoint.rst:39
msgid "0.333"
#: ../../tutorial/floatingpoint.rst:41
"and so on.  No matter how many digits you're willing to write down, the "
"result will never be exactly 1/3, but will be an increasingly better "
"approximation of 1/3."
#: ../../tutorial/floatingpoint.rst:45
"In the same way, no matter how many base 2 digits you're willing to use, the "
"decimal value 0.1 cannot be represented exactly as a base 2 fraction.  In "
"base 2, 1/10 is the infinitely repeating fraction ::"
#: ../../tutorial/floatingpoint.rst:49
#: ../../tutorial/floatingpoint.rst:51
"Stop at any finite number of bits, and you get an approximation.  On most "
"machines today, floats are approximated using a binary fraction with the "
"numerator using the first 53 bits starting with the most significant bit and "
"with the denominator as a power of two.  In the case of 1/10, the binary "
"fraction is ``3602879701896397 / 2 ** 55`` which is close to but not exactly "
"equal to the true value of 1/10."
#: ../../tutorial/floatingpoint.rst:58
"Many users are not aware of the approximation because of the way values are "
"displayed.  Python only prints a decimal approximation to the true decimal "
"value of the binary approximation stored by the machine.  On most machines, "
"if Python were to print the true decimal value of the binary approximation "
"stored for 0.1, it would have to display::"
#: ../../tutorial/floatingpoint.rst:64
">>> 0.1\n"
#: ../../tutorial/floatingpoint.rst:67
"That is more digits than most people find useful, so Python keeps the number "
"of digits manageable by displaying a rounded value instead:"
#: ../../tutorial/floatingpoint.rst:70
">>> 1 / 10\n"
#: ../../tutorial/floatingpoint.rst:75
"Just remember, even though the printed result looks like the exact value of "
"1/10, the actual stored value is the nearest representable binary fraction."
#: ../../tutorial/floatingpoint.rst:78
"Interestingly, there are many different decimal numbers that share the same "
"nearest approximate binary fraction.  For example, the numbers ``0.1`` and "
"``0.10000000000000001`` and "
"approximated by ``3602879701896397 / 2 ** 55``.  Since all of these decimal "
"values share the same approximation, any one of them could be displayed "
"while still preserving the invariant ``eval(repr(x)) == x``."
#: ../../tutorial/floatingpoint.rst:86
"Historically, the Python prompt and built-in :func:`repr` function would "
"choose the one with 17 significant digits, ``0.10000000000000001``.   "
"Starting with Python 3.1, Python (on most systems) is now able to choose the "
"shortest of these and simply display ``0.1``."
#: ../../tutorial/floatingpoint.rst:91
"Note that this is in the very nature of binary floating point: this is not a "
"bug in Python, and it is not a bug in your code either.  You'll see the same "
"kind of thing in all languages that support your hardware's floating-point "
"arithmetic (although some languages may not *display* the difference by "
"default, or in all output modes)."
#: ../../tutorial/floatingpoint.rst:97
"For more pleasant output, you may wish to use string formatting to produce a "
"limited number of significant digits:"
#: ../../tutorial/floatingpoint.rst:100
">>> format(math.pi, '.12g')  # give 12 significant digits\n"
"'3.14159265359'\n"
">>> format(math.pi, '.2f')   # give 2 digits after the point\n"
">>> repr(math.pi)\n"
"'3.141592653589793'"
#: ../../tutorial/floatingpoint.rst:111
"It's important to realize that this is, in a real sense, an illusion: you're "
"simply rounding the *display* of the true machine value."
#: ../../tutorial/floatingpoint.rst:114
"One illusion may beget another.  For example, since 0.1 is not exactly 1/10, "
"summing three values of 0.1 may not yield exactly 0.3, either:"
#: ../../tutorial/floatingpoint.rst:117
">>> 0.1 + 0.1 + 0.1 == 0.3\n"
#: ../../tutorial/floatingpoint.rst:122
"Also, since the 0.1 cannot get any closer to the exact value of 1/10 and 0.3 "
"cannot get any closer to the exact value of 3/10, then pre-rounding "
"with :func:`round` function cannot help:"
#: ../../tutorial/floatingpoint.rst:126
">>> round(0.1, 1) + round(0.1, 1) + round(0.1, 1) == round(0.3, 1)\n"
#: ../../tutorial/floatingpoint.rst:131
"Though the numbers cannot be made closer to their intended exact values, "
"the :func:`math.isclose` function can be useful for comparing inexact values:"
#: ../../tutorial/floatingpoint.rst:134
">>> math.isclose(0.1 + 0.1 + 0.1, 0.3)\n"
#: ../../tutorial/floatingpoint.rst:139
"Alternatively, the :func:`round` function can be used to compare rough "
"approximations:"
#: ../../tutorial/floatingpoint.rst:142
">>> round(math.pi, ndigits=2) == round(22 / 7, ndigits=2)\n"
#: ../../tutorial/floatingpoint.rst:147
"Binary floating-point arithmetic holds many surprises like this.  The "
"problem with \"0.1\" is explained in precise detail below, in the "
"\"Representation Error\" section.  See `Examples of Floating Point Problems "
"<https://jvns.ca/blog/2023/01/13/examples-of-floating-point-problems/>`_ for "
"a pleasant summary of how binary floating point works and the kinds of "
"problems commonly encountered in practice.  Also see `The Perils of Floating "
"Point <http://www.indowsway.com/floatingpoint.htm>`_ for a more complete "
"account of other common surprises."
#: ../../tutorial/floatingpoint.rst:156
"As that says near the end, \"there are no easy answers.\"  Still, don't be "
"unduly wary of floating point!  The errors in Python float operations are "
"inherited from the floating-point hardware, and on most machines are on the "
"order of no more than 1 part in 2\\*\\*53 per operation.  That's more than "
"adequate for most tasks, but you do need to keep in mind that it's not "
"decimal arithmetic and that every float operation can suffer a new rounding "
#: ../../tutorial/floatingpoint.rst:163
"While pathological cases do exist, for most casual use of floating-point "
"arithmetic you'll see the result you expect in the end if you simply round "
"the display of your final results to the number of decimal digits you "
"expect. :func:`str` usually suffices, and for finer control see "
"the :meth:`str.format` method's format specifiers in :ref:`formatstrings`."
#: ../../tutorial/floatingpoint.rst:169
"For use cases which require exact decimal representation, try using "
"the :mod:`decimal` module which implements decimal arithmetic suitable for "
"accounting applications and high-precision applications."
#: ../../tutorial/floatingpoint.rst:173
"Another form of exact arithmetic is supported by the :mod:`fractions` module "
"which implements arithmetic based on rational numbers (so the numbers like "
"1/3 can be represented exactly)."
#: ../../tutorial/floatingpoint.rst:177
"If you are a heavy user of floating-point operations you should take a look "
"at the NumPy package and many other packages for mathematical and "
"statistical operations supplied by the SciPy project. See <https://"
"scipy.org>."
#: ../../tutorial/floatingpoint.rst:181
"Python provides tools that may help on those rare occasions when you really "
"*do* want to know the exact value of a float.  "
"The :meth:`float.as_integer_ratio` method expresses the value of a float as "
"a fraction:"
#: ../../tutorial/floatingpoint.rst:186
">>> x = 3.14159\n"
">>> x.as_integer_ratio()\n"
#: ../../tutorial/floatingpoint.rst:192
"Since the ratio is exact, it can be used to losslessly recreate the original "
#: ../../tutorial/floatingpoint.rst:195
">>> x == 3537115888337719 / 1125899906842624\n"
#: ../../tutorial/floatingpoint.rst:200
"The :meth:`float.hex` method expresses a float in hexadecimal (base 16), "
"again giving the exact value stored by your computer:"
#: ../../tutorial/floatingpoint.rst:203
">>> x.hex()\n"
"'0x1.921f9f01b866ep+1'"
#: ../../tutorial/floatingpoint.rst:208
"This precise hexadecimal representation can be used to reconstruct the float "
"value exactly:"
#: ../../tutorial/floatingpoint.rst:211
">>> x == float.fromhex('0x1.921f9f01b866ep+1')\n"
#: ../../tutorial/floatingpoint.rst:216
"Since the representation is exact, it is useful for reliably porting values "
"across different versions of Python (platform independence) and exchanging "
"data with other languages that support the same format (such as Java and "
#: ../../tutorial/floatingpoint.rst:220
"Another helpful tool is the :func:`sum` function which helps mitigate loss-"
"of-precision during summation.  It uses extended precision for intermediate "
"rounding steps as values are added onto a running total. That can make a "
"difference in overall accuracy so that the errors do not accumulate to the "
"point where they affect the final total:"
#: ../../tutorial/floatingpoint.rst:226
">>> 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 == 1.0\n"
">>> sum([0.1] * 10) == 1.0\n"
#: ../../tutorial/floatingpoint.rst:233
"The :func:`math.fsum` goes further and tracks all of the \"lost digits\" as "
"values are added onto a running total so that the result has only a single "
"rounding.  This is slower than :func:`sum` but will be more accurate in "
"uncommon cases where large magnitude inputs mostly cancel each other out "
"leaving a final sum near zero:"
#: ../../tutorial/floatingpoint.rst:239
">>> arr = [-0.10430216751806065, -266310978.67179024, 143401161448607.16,\n"
">>> float(sum(map(Fraction, arr)))   # Exact summation with single rounding\n"
"8.042173697819788e-13\n"
">>> math.fsum(arr)                   # Single rounding\n"
"8.042173697819788e-13\n"
">>> sum(arr)                         # Multiple roundings in extended "
"precision\n"
"8.042178034628478e-13\n"
">>> total = 0.0\n"
">>> for x in arr:\n"
"...     total += x                   # Multiple roundings in standard "
"precision\n"
">>> total                            # Straight addition has no correct "
"digits!\n"
#: ../../tutorial/floatingpoint.rst:260
msgid "Representation Error"
#: ../../tutorial/floatingpoint.rst:262
"This section explains the \"0.1\" example in detail, and shows how you can "
"perform an exact analysis of cases like this yourself.  Basic familiarity "
"with binary floating-point representation is assumed."
#: ../../tutorial/floatingpoint.rst:266
":dfn:`Representation error` refers to the fact that some (most, actually) "
"decimal fractions cannot be represented exactly as binary (base 2) "
"fractions. This is the chief reason why Python (or Perl, C, C++, Java, "
"Fortran, and many others) often won't display the exact decimal number you "
#: ../../tutorial/floatingpoint.rst:271
"Why is that?  1/10 is not exactly representable as a binary fraction.  Since "
"at least 2000, almost all machines use IEEE 754 binary floating-point "
"arithmetic, and almost all platforms map Python floats to IEEE 754 binary64 "
"\"double precision\" values.  IEEE 754 binary64 values contain 53 bits of "
"precision, so on input the computer strives to convert 0.1 to the closest "
"fraction it can of the form *J*/2**\\ *N* where *J* is an integer containing "
"exactly 53 bits. Rewriting ::"
#: ../../tutorial/floatingpoint.rst:280
msgid "1 / 10 ~= J / (2**N)"
#: ../../tutorial/floatingpoint.rst:282
msgid "as ::"
#: ../../tutorial/floatingpoint.rst:284
msgid "J ~= 2**N / 10"
#: ../../tutorial/floatingpoint.rst:286
"and recalling that *J* has exactly 53 bits (is ``>= 2**52`` but ``< "
"2**53``), the best value for *N* is 56:"
#: ../../tutorial/floatingpoint.rst:289
">>> 2**52 <=  2**56 // 10  < 2**53\n"
#: ../../tutorial/floatingpoint.rst:294
"That is, 56 is the only value for *N* that leaves *J* with exactly 53 bits.  "
"The best possible value for *J* is then that quotient rounded:"
#: ../../tutorial/floatingpoint.rst:297
">>> q, r = divmod(2**56, 10)\n"
#: ../../tutorial/floatingpoint.rst:303
"Since the remainder is more than half of 10, the best approximation is "
"obtained by rounding up:"
#: ../../tutorial/floatingpoint.rst:306
">>> q+1\n"
#: ../../tutorial/floatingpoint.rst:313
"Therefore the best possible approximation to 1/10 in IEEE 754 double "
"precision is::"
#: ../../tutorial/floatingpoint.rst:316
msgid "7205759403792794 / 2 ** 56"
#: ../../tutorial/floatingpoint.rst:318
"Dividing both the numerator and denominator by two reduces the fraction to::"
#: ../../tutorial/floatingpoint.rst:320
msgid "3602879701896397 / 2 ** 55"
#: ../../tutorial/floatingpoint.rst:322
"Note that since we rounded up, this is actually a little bit larger than "
"1/10; if we had not rounded up, the quotient would have been a little bit "
"smaller than 1/10.  But in no case can it be *exactly* 1/10!"
#: ../../tutorial/floatingpoint.rst:326
"So the computer never \"sees\" 1/10:  what it sees is the exact fraction "
"given above, the best IEEE 754 double approximation it can get:"
#: ../../tutorial/floatingpoint.rst:329
">>> 0.1 * 2 ** 55\n"
#: ../../tutorial/floatingpoint.rst:334
"If we multiply that fraction by 10\\*\\*55, we can see the value out to 55 "
"decimal digits:"
#: ../../tutorial/floatingpoint.rst:337
">>> 3602879701896397 * 10 ** 55 // 2 ** 55\n"
#: ../../tutorial/floatingpoint.rst:342
"meaning that the exact number stored in the computer is equal to the decimal "
"value 0.1000000000000000055511151231257827021181583404541015625. Instead of "
"displaying the full decimal value, many languages (including older versions "
"of Python), round the result to 17 significant digits:"
#: ../../tutorial/floatingpoint.rst:347
">>> format(0.1, '.17f')\n"
"'0.10000000000000001'"
#: ../../tutorial/floatingpoint.rst:352
"The :mod:`fractions` and :mod:`decimal` modules make these calculations easy:"
#: ../../tutorial/floatingpoint.rst:355
">>> from decimal import Decimal\n"
">>> from fractions import Fraction\n"
">>> Fraction.from_float(0.1)\n"
"Fraction(3602879701896397, 36028797018963968)\n"
">>> (0.1).as_integer_ratio()\n"
">>> Decimal.from_float(0.1)\n"
"Decimal('0.1000000000000000055511151231257827021181583404541015625')\n"
">>> format(Decimal.from_float(0.1), '.17')\n"
"'0.10000000000000001'"
Sunbelt Computer Software

PL/B Language Development and Support

Navigation Menu

Uh oh!

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

FilesExpand file tree

floatingpoint.po

Latest commit

History

floatingpoint.po

File metadata and controls
