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 csernazs, eric.smith, mark.dickinson
Date 2010-02-11.15:14:11
SpamBayes Score 6.4093175e-13
Marked as misclassified No
Message-id <1265901253.88.0.457076086167.issue7906@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the report, and for the analysis.

I'd call this a bug in the Solaris strtod function (though that doesn't preclude adding a workaround for Python):  the C standards (well, C99, anyway;  I don't have access to C89 at the moment) enumerate clearly which strings are permitted, and "INFI" isn't among them.

string <-> float conversions got significantly reworked for Python 2.7 and 3.1, so there shouldn't be any problem with those versions.  Are you in a position to confirm this?

It would be fairly easy to work around this strtod issue by backporting the _Py_parse_inf_or_nan and case_insensitive match functions (in Python/pystrtod.c) from trunk to Python 2.6, and using those functions in PyOS_ascii_strtod.
History
Date User Action Args
2010-02-11 15:14:14mark.dickinsonsetrecipients: + mark.dickinson, csernazs, eric.smith
2010-02-11 15:14:13mark.dickinsonsetmessageid: <1265901253.88.0.457076086167.issue7906@psf.upfronthosting.co.za>
2010-02-11 15:14:12mark.dickinsonlinkissue7906 messages
2010-02-11 15:14:11mark.dickinsoncreate