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 Alexander.Belopolsky, Arfrever, belopolsky, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall, skrah, vstinner
Date 2011-09-10.11:37:52
SpamBayes Score 0.031594
Marked as misclassified No
Message-id <>
[about adding float128]
> I realize a new float type would be a major undertaking

That's an understatement and a half.  The only way this could ever be viable is if float128 support becomes widespread enough that we don't have to write our own algorithms for basic float128 operations;  even then, it would still be a massive undertaking.  MPFR provides these operations, but it's LGPL.

I don't see this happening in the forseeable future.
Date User Action Args
2011-09-10 11:37:53mark.dickinsonsetrecipients: + mark.dickinson, loewis, jcea, belopolsky, lars.gustaebel, vstinner, larry, nadeem.vawda, Arfrever, r.david.murray, skrah, Alexander.Belopolsky, rosslagerwall, khenriksson
2011-09-10 11:37:53mark.dickinsonsetmessageid: <>
2011-09-10 11:37:53mark.dickinsonlinkissue11457 messages
2011-09-10 11:37:52mark.dickinsoncreate