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 terry.reedy
Recipients MrJean1, mark.dickinson, rhettinger, terry.reedy, tim.peters
Date 2008-08-02.20:16:55
SpamBayes Score 0.152866
Marked as misclassified No
Message-id <4894C0B5.1000408@udel.edu>
In-reply-to <1217667434.47.0.770731192577.issue2819@psf.upfronthosting.co.za>
Content
> I'm pretty sure it *was* merged:  math.sum should be the full-precision 
> summation in both recent betas (2.6b2 and 3.0b2).  Try comparing
> sum([1e100, 1, -1e100, -1]) and math.sum([1e100, 1, -1e100, -1])---they 
> should produce -1.0 and 0.0 respectively.

They do.  I realize now that two different built-in funcs in two 
different modules but with the same name will give the same 
representation.  That is so unusual, I was not expecting it.

> The name change to fsum only happened in the last few days.

Which will prevent the confusion I had ;-).  Good idea.
History
Date User Action Args
2008-08-02 20:16:57terry.reedysetrecipients: + terry.reedy, tim.peters, rhettinger, mark.dickinson, MrJean1
2008-08-02 20:16:56terry.reedylinkissue2819 messages
2008-08-02 20:16:55terry.reedycreate