@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.13\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2025-11-19 15:26 +0000\n "
15+ "POT-Creation-Date : 2025-11-29 15:01 +0000\n "
1616"PO-Revision-Date : 2025-09-15 01:04+0000\n "
1717"Last-Translator : Vladimir, 2025\n "
1818"Language-Team : Russian (https://app.transifex.com/python-doc/teams/5390/ru/)\n "
@@ -2418,37 +2418,37 @@ msgstr ""
24182418
24192419#: ../../library/decimal.rst:2070
24202420msgid ""
2421- "Q. It is cumbersome to type ``decimal.Decimal('1234.5')``. Is there a way "
2421+ "Q: It is cumbersome to type ``decimal.Decimal('1234.5')``. Is there a way "
24222422"to minimize typing when using the interactive interpreter?"
24232423msgstr ""
24242424
24252425#: ../../library/decimal.rst:2073
2426- msgid "A. Some users abbreviate the constructor to just a single letter:"
2426+ msgid "A: Some users abbreviate the constructor to just a single letter:"
24272427msgstr ""
24282428
24292429#: ../../library/decimal.rst:2079
24302430msgid ""
2431- "Q. In a fixed-point application with two decimal places, some inputs have "
2431+ "Q: In a fixed-point application with two decimal places, some inputs have "
24322432"many places and need to be rounded. Others are not supposed to have excess "
24332433"digits and need to be validated. What methods should be used?"
24342434msgstr ""
24352435
24362436#: ../../library/decimal.rst:2083
24372437msgid ""
2438- "A. The :meth:`~Decimal.quantize` method rounds to a fixed number of decimal "
2438+ "A: The :meth:`~Decimal.quantize` method rounds to a fixed number of decimal "
24392439"places. If the :const:`Inexact` trap is set, it is also useful for "
24402440"validation:"
24412441msgstr ""
24422442
24432443#: ../../library/decimal.rst:2101
24442444msgid ""
2445- "Q. Once I have valid two place inputs, how do I maintain that invariant "
2445+ "Q: Once I have valid two place inputs, how do I maintain that invariant "
24462446"throughout an application?"
24472447msgstr ""
24482448
24492449#: ../../library/decimal.rst:2104
24502450msgid ""
2451- "A. Some operations like addition, subtraction, and multiplication by an "
2451+ "A: Some operations like addition, subtraction, and multiplication by an "
24522452"integer will automatically preserve fixed point. Others operations, like "
24532453"division and non-integer multiplication, will change the number of decimal "
24542454"places and need to be followed-up with a :meth:`~Decimal.quantize` step:"
@@ -2462,25 +2462,25 @@ msgstr ""
24622462
24632463#: ../../library/decimal.rst:2136
24642464msgid ""
2465- "Q. There are many ways to express the same value. The numbers ``200``, "
2465+ "Q: There are many ways to express the same value. The numbers ``200``, "
24662466"``200.000``, ``2E2``, and ``.02E+4`` all have the same value at various "
24672467"precisions. Is there a way to transform them to a single recognizable "
24682468"canonical value?"
24692469msgstr ""
24702470
24712471#: ../../library/decimal.rst:2141
24722472msgid ""
2473- "A. The :meth:`~Decimal.normalize` method maps all equivalent values to a "
2473+ "A: The :meth:`~Decimal.normalize` method maps all equivalent values to a "
24742474"single representative:"
24752475msgstr ""
24762476
24772477#: ../../library/decimal.rst:2148
2478- msgid "Q. When does rounding occur in a computation?"
2478+ msgid "Q: When does rounding occur in a computation?"
24792479msgstr ""
24802480
24812481#: ../../library/decimal.rst:2150
24822482msgid ""
2483- "A. It occurs *after* the computation. The philosophy of the decimal "
2483+ "A: It occurs *after* the computation. The philosophy of the decimal "
24842484"specification is that numbers are considered exact and are created "
24852485"independent of the current context. They can even have greater precision "
24862486"than current context. Computations process with those exact inputs and then"
@@ -2504,13 +2504,13 @@ msgstr ""
25042504
25052505#: ../../library/decimal.rst:2168
25062506msgid ""
2507- "Q. Some decimal values always print with exponential notation. Is there a "
2507+ "Q: Some decimal values always print with exponential notation. Is there a "
25082508"way to get a non-exponential representation?"
25092509msgstr ""
25102510
25112511#: ../../library/decimal.rst:2171
25122512msgid ""
2513- "A. For some values, exponential notation is the only way to express the "
2513+ "A: For some values, exponential notation is the only way to express the "
25142514"number of significant places in the coefficient. For example, expressing "
25152515"``5.0E+3`` as ``5000`` keeps the value constant but cannot show the "
25162516"original's two-place significance."
@@ -2524,12 +2524,12 @@ msgid ""
25242524msgstr ""
25252525
25262526#: ../../library/decimal.rst:2186
2527- msgid "Q. Is there a way to convert a regular float to a :class:`Decimal`?"
2527+ msgid "Q: Is there a way to convert a regular float to a :class:`Decimal`?"
25282528msgstr ""
25292529
25302530#: ../../library/decimal.rst:2188
25312531msgid ""
2532- "A. Yes, any binary floating-point number can be exactly expressed as a "
2532+ "A: Yes, any binary floating-point number can be exactly expressed as a "
25332533"Decimal though an exact conversion may take more precision than intuition "
25342534"would suggest:"
25352535msgstr ""
@@ -2542,28 +2542,28 @@ msgstr ""
25422542
25432543#: ../../library/decimal.rst:2197
25442544msgid ""
2545- "Q. Within a complex calculation, how can I make sure that I haven't gotten a"
2545+ "Q: Within a complex calculation, how can I make sure that I haven't gotten a"
25462546" spurious result because of insufficient precision or rounding anomalies."
25472547msgstr ""
25482548
25492549#: ../../library/decimal.rst:2200
25502550msgid ""
2551- "A. The decimal module makes it easy to test results. A best practice is to "
2551+ "A: The decimal module makes it easy to test results. A best practice is to "
25522552"re-run calculations using greater precision and with various rounding modes."
25532553" Widely differing results indicate insufficient precision, rounding mode "
25542554"issues, ill-conditioned inputs, or a numerically unstable algorithm."
25552555msgstr ""
25562556
25572557#: ../../library/decimal.rst:2205
25582558msgid ""
2559- "Q. I noticed that context precision is applied to the results of operations "
2559+ "Q: I noticed that context precision is applied to the results of operations "
25602560"but not to the inputs. Is there anything to watch out for when mixing "
25612561"values of different precisions?"
25622562msgstr ""
25632563
25642564#: ../../library/decimal.rst:2209
25652565msgid ""
2566- "A. Yes. The principle is that all values are considered to be exact and so "
2566+ "A: Yes. The principle is that all values are considered to be exact and so "
25672567"is the arithmetic on those values. Only the results are rounded. The "
25682568"advantage for inputs is that \" what you type is what you get\" . A "
25692569"disadvantage is that the results can look odd if you forget that the inputs "
@@ -2599,12 +2599,12 @@ msgid ""
25992599msgstr ""
26002600
26012601#: ../../library/decimal.rst:2237
2602- msgid "Q. Is the CPython implementation fast for large numbers?"
2602+ msgid "Q: Is the CPython implementation fast for large numbers?"
26032603msgstr ""
26042604
26052605#: ../../library/decimal.rst:2239
26062606msgid ""
2607- "A. Yes. In the CPython and PyPy3 implementations, the C/CFFI versions of "
2607+ "A: Yes. In the CPython and PyPy3 implementations, the C/CFFI versions of "
26082608"the decimal module integrate the high speed `libmpdec "
26092609"<https://www.bytereef.org/mpdecimal/doc/libmpdec/index.html>`_ library for "
26102610"arbitrary precision correctly rounded decimal floating-point arithmetic "
0 commit comments