Here's a patch that adds a PyOS_string_to_double function to complement the recently added PyOS_double_to_string function.This is supposed to be a more Pythonic version of PyOS_ascii_strtod.  It raises Python exceptions to correspond to the various possible errors (malformed string, overflowing number, malloc failure...) instead of requiring the caller to examine errno.It's intended for both internal and external use;  if this goes in, I intend to use it in the Python core in places where PyOS_ascii_strtod or PyOS_ascii_atof are currently used.

This looks okay to me (although since it's not hooked up I haven'ttested it). I particularly like that it doesn't allow leadingwhitespace, and that the caller no longer has to remember errno(forgetting to set and/or test it have both caused me problems in the past).Does the whitespace change cause any problems for any internal code? Iwouldn't think so, but I haven't looked at it.As long as you're at it, I'd suggest deprecating PyOS_ascii_*.

Thanks for the feedback!Here's an updated patch that also deprecates PyOS_ascii_strtod and PyOS_ascii_atof and hooks up PyOS_string_to_double everywhere.  The documentation still needs proper markup, and I'll add some C-API tests.

This looks okay to me, and passes the tests.In PyOS_string_to_double, you can simplify it by using PyErr_Formatinstead of printing into a buffer and using PyErr_SetString. Sorry Ididn't catch this earlier.

Thanks.  I've committed a version of this patch, with Eric's suggested PyErr_Format change, inr72248.