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 amaury.forgeotdarc, djc, eric.smith, mark.dickinson, michael.foord, rhettinger, vstinner
Date 2011-07-01.07:13:20
SpamBayes Score 0.0004913477
Marked as misclassified No
Message-id <1309504400.94.0.794709408739.issue12450@psf.upfronthosting.co.za>
In-reply-to
Content
[Amaury]
"It would be interesting to see if it is better/faster than the current dtoa."

I agree that it would be interesting to compare.

[Eric]
"maybe we can say we we can live with 99.5% shortest repr coverage"

Please no!  As you say, we'd still need the fallback code.

For me, a precondition for actually switching (rather than just investigating speed differences) would be that the Grisu3 code has excellent tests.  The dtoa.c code is still pretty hairy in places but is now fairly well tested and inspected;  I'd hesitate to replace that with something less well exercised.
History
Date User Action Args
2011-07-01 07:13:21mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, amaury.forgeotdarc, vstinner, eric.smith, djc, michael.foord
2011-07-01 07:13:20mark.dickinsonsetmessageid: <1309504400.94.0.794709408739.issue12450@psf.upfronthosting.co.za>
2011-07-01 07:13:20mark.dickinsonlinkissue12450 messages
2011-07-01 07:13:20mark.dickinsoncreate