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 mark.dickinson
Recipients mark.dickinson, segfaulthunter
Date 2008-09-03.16:07:59
SpamBayes Score 4.5911514e-05
Marked as misclassified No
Message-id <1220458080.91.0.727690742719.issue3724@psf.upfronthosting.co.za>
In-reply-to
Content
I can't really see a compelling reason to make this change---it
seems like an unnecessary complication to add to what's currently
a simple function.  Someone who really needs the accuracy can
just use log10.  Perhaps a note in the documentation for log
suggesting this would be useful.

I guess this solution seems insufficiently general:  why 'fix'
log(x, 10) but not log(x, 2), for example?

OTOH, a two-argument log that was guaranteed correctly rounded
(or accurate to within 1ulp) for *all* bases would certainly
be of interest!  But that's a fairly major project...
History
Date User Action Args
2008-09-03 16:08:01mark.dickinsonsetrecipients: + mark.dickinson, segfaulthunter
2008-09-03 16:08:00mark.dickinsonsetmessageid: <1220458080.91.0.727690742719.issue3724@psf.upfronthosting.co.za>
2008-09-03 16:08:00mark.dickinsonlinkissue3724 messages
2008-09-03 16:07:59mark.dickinsoncreate