This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients MrJean1, mark.dickinson, rhettinger, tim.peters
Date 2008-08-01.19:16:27
SpamBayes Score 5.47736e-05
Marked as misclassified No
Message-id <1217618189.51.0.150426240402.issue2819@psf.upfronthosting.co.za>
In-reply-to
Content
Mark, changing API is something to avoid after beta cycles begin (so,
e.g., it's late in the game to /add/ a new API, like a new method for
complex summation).  But there's no particular reason to fear changing
implementation for an API that's already in.  If the test suite supplies
good coverage, the buildbots will catch significant portability snafus
in plenty of time for the next release.

The big attraction to the lsum-like approach for users is that it "just
works", without requiring weasel words in the docs about overflows,
underflows, or esoteric details about various HW FP quirks.  Integer
arithmetic is just plain better behaved across platforms ;-)
History
Date User Action Args
2008-08-01 19:16:29tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, MrJean1
2008-08-01 19:16:29tim.peterssetmessageid: <1217618189.51.0.150426240402.issue2819@psf.upfronthosting.co.za>
2008-08-01 19:16:28tim.peterslinkissue2819 messages
2008-08-01 19:16:27tim.peterscreate