A suggestion to change decimal module docstring
Not worth a tracker entry, so I am just sending this to docs and Mark. I find current "(for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of the expected Decimal("0.00") returned by decimal floating point)" in the introduction a bit unclear because neither Decimal class nor it's constructor taking a string has been introduced by that point. I think it is better to just use 0.00 for the "expected" value.
Suggested replacement text: [...] expectations that are at odds with binary floating point (for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of 0.0; Decimal('1.00') % Decimal('0.1') returns the expected Decimal('0.00')). On Sat, Jun 12, 2010 at 4:41 AM, Alexander Belopolsky <alexander.belopolsky@gmail.com> wrote:
Not worth a tracker entry, so I am just sending this to docs and Mark.
I find current "(for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of the expected Decimal("0.00") returned by decimal floating point)" in the introduction a bit unclear because neither Decimal class nor it's constructor taking a string has been introduced by that point. I think it is better to just use 0.00 for the "expected" value.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sounds good... someone please apply. Georg Am 12.06.2010 11:05, schrieb Mark Dickinson:
Suggested replacement text:
[...] expectations that are at odds with binary floating point (for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of 0.0; Decimal('1.00') % Decimal('0.1') returns the expected Decimal('0.00')).
On Sat, Jun 12, 2010 at 4:41 AM, Alexander Belopolsky <alexander.belopolsky@gmail.com> wrote:
Not worth a tracker entry, so I am just sending this to docs and Mark.
I find current "(for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of the expected Decimal("0.00") returned by decimal floating point)" in the introduction a bit unclear because neither Decimal class nor it's constructor taking a string has been introduced by that point. I think it is better to just use 0.00 for the "expected" value.
_______________________________________________ docs mailing list docs@python.org http://mail.python.org/mailman/listinfo/docs
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEARECAAYFAkwTs90ACgkQN9GcIYhpnLBHywCgqbZEsaaN+yMWNMqWYsICzNFY HOgAnAotmwuhnYBoOiGxFZIHyIAQI/NF =OXX9 -----END PGP SIGNATURE-----
Done in r81951. Mark On Sat, Jun 12, 2010 at 5:20 PM, Georg Brandl <georg@python.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Sounds good... someone please apply.
Georg
Am 12.06.2010 11:05, schrieb Mark Dickinson:
Suggested replacement text:
[...] expectations that are at odds with binary floating point (for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of 0.0; Decimal('1.00') % Decimal('0.1') returns the expected Decimal('0.00')).
On Sat, Jun 12, 2010 at 4:41 AM, Alexander Belopolsky <alexander.belopolsky@gmail.com> wrote:
Not worth a tracker entry, so I am just sending this to docs and Mark.
I find current "(for instance, in binary floating point, 1.00 % 0.1 gives 0.09999999999999995 instead of the expected Decimal("0.00") returned by decimal floating point)" in the introduction a bit unclear because neither Decimal class nor it's constructor taking a string has been introduced by that point. I think it is better to just use 0.00 for the "expected" value.
_______________________________________________ docs mailing list docs@python.org http://mail.python.org/mailman/listinfo/docs
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux)
iEYEARECAAYFAkwTs90ACgkQN9GcIYhpnLBHywCgqbZEsaaN+yMWNMqWYsICzNFY HOgAnAotmwuhnYBoOiGxFZIHyIAQI/NF =OXX9 -----END PGP SIGNATURE-----
participants (3)
-
Alexander Belopolsky -
Georg Brandl -
Mark Dickinson