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 brian.curtin, eudoxos, loewis, mark.dickinson, petri.lehtinen, schmir, tim.golden
Date 2012-10-30.10:16:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351592171.58.0.759577950129.issue11566@psf.upfronthosting.co.za>
In-reply-to
Content
I think there's something generally smelly about the way hypot is handled;  this isn't the only hypot-related build issue that's turned up.  I'm wondering whether the code can be reworked to deal with hypot in the same way that functions like log1p, etc. are dealt with in the math module---i.e., define a _Py_hypot wrapper function, and use that everywhere internally.  One difference is that log1p is only used in cmath and math, while hypot is also needed in the Python core.
History
Date User Action Args
2012-10-30 10:16:11mark.dickinsonsetrecipients: + mark.dickinson, loewis, schmir, tim.golden, brian.curtin, petri.lehtinen, eudoxos
2012-10-30 10:16:11mark.dickinsonsetmessageid: <1351592171.58.0.759577950129.issue11566@psf.upfronthosting.co.za>
2012-10-30 10:16:11mark.dickinsonlinkissue11566 messages
2012-10-30 10:16:11mark.dickinsoncreate