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 nirinA
Recipients mark.dickinson, nirinA, rhettinger, stutzbach, terry.reedy
Date 2008-07-25.00:33:26
SpamBayes Score 0.0017301984
Marked as misclassified No
Message-id <>
Mark Dickinson :
> So a full patch for this should touch at least Python/pymath.c, 
> Modules/mathmodule.c,, Lib/test/, and 
> Doc/Library/math.rst.
here are patches for Python/pymath.c, Modules/mathmodule.c,
Lib/test/, Doc/Library/math.rst and also Include/pymath.h.
i haven't touched as i've erf, erfc, lgamma and tgamma
on my platform, so the patches can be tested.
the doc may need better wording and some additionnal tests.

Raymond Hettinger:
> It would be nice if we knew the error bounds for each of the 
> approximation methods. Do we know how the coefficients were generated?
it will be really great if we're able to regenerate all these
coefficients. this may be done by following the comments in
the original codes, but not that easy and not sure one will obtain
the same things.

> The lowword/highword macros look to be tightly tied to the internal 
> processor representation for floats.  It would be more portable and 
> maintainable to replace that bit twiddling with something based on frexp
it seems possible to avoid the use of these macros.
i'll try to find time to dig up these possibilities.
Date User Action Args
2008-07-25 00:33:29nirinAsetspambayes_score: 0.0017302 -> 0.0017301984
recipients: + nirinA, rhettinger, terry.reedy, mark.dickinson, stutzbach
2008-07-25 00:33:29nirinAsetspambayes_score: 0.0017302 -> 0.0017302
messageid: <>
2008-07-25 00:33:28nirinAlinkissue3366 messages
2008-07-25 00:33:26nirinAcreate