[issue13731] Awkward phrasing in Decimal documentation

Raymond Hettinger added the comment: No problem. Thanks for showing an interest in the quality of the documentation. -- resolution: -> rejected status: open -> closed ___ Python tracker _

[issue13731] Awkward phrasing in Decimal documentation

Aaron Maenpaa added the comment: I can understand what was meant. You're welcome to close the issue. Sorry for the nitpick. -- ___ Python tracker ___ __

[issue13731] Awkward phrasing in Decimal documentation

Raymond Hettinger added the comment: If you can't ascertain the meaning of the sentence, I'll consider making a change. Itherwise, this appears to have degenerated into trivial micro-wordsmithing and I'll close this as not being worth consuming any more of my time. -- _

[issue13731] Awkward phrasing in Decimal documentation

Aaron Maenpaa added the comment: That's fine. I'm not particularly attached to that phrasing. The one thing I would push for is to add a comma to "... decimal is preferred in accounting applications which have strict equality invariants." ... since, as far as I can tell, "which have strict eq

[issue13731] Awkward phrasing in Decimal documentation

Raymond Hettinger added the comment: I'm sorry but I think the current wording is better that your proposed revision. When I get a chance, I'll revisit it to see if I can find another way to improve the text. -- priority: normal -> low ___ Python t

[issue13731] Awkward phrasing in Decimal documentation

Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list ma

[issue13731] Awkward phrasing in Decimal documentation

New submission from Aaron Maenpaa : The paragraph: "The exactness carries over into arithmetic. In decimal floating point, 0.1 + 0.1 + 0.1 - 0.3 is exactly equal to zero. In binary floating point, the result is 5.5511151231257827e-017. While near to zero, the differences prevent reliable equal