[issue18062] m68k FPU precision issue

Mark Dickinson report at bugs.python.org
Sun May 26 12:16:44 CEST 2013


Mark Dickinson added the comment:

It's also an option not to use dtoa.c:  Python still has fallback code that uses the OS double <-> char* conversions for the case where the configuration step can't figure out how to change the FPU control word.  In that case compilation should still succeed, and the resulting Python would show:

>>> import sys
>>> sys.float_repr_style
'legacy'

If there are tests failing with the 'legacy' mode, that may just indicate buggy tests that haven't been properly marked as depending on the short float repr.  (E.g., by decorating with "@unittest.skipUnless(getattr(sys, 'float_repr_style', '') == 'short'"), or poorly-designed tests that could be rewritten.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18062>
_______________________________________


More information about the Python-bugs-list mailing list