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 benjamin.peterson, ezio.melotti, hieu.nguyen, mark.dickinson
Date 2012-10-26.17:55:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
What use-cases did you have in mind for this?  (I assume that something motivated this report.)

It seems to me that there's not actually much to say about the float format:  the only format that Python realistically supports these days is the IEEE 754 binary64 format.  (In theory we still support whatever C uses, but in practice I suspect that if we were ever to manage to run Python on a machine whose C doubles *weren't* in binary64 format, we'd see quite a lot of breakage.)

So the only variation that we'll see is little-endian versus big-endian.  We don't even support the ARM OABI mixed-endian format.  Should endianness be considered an important part of the format?
Date User Action Args
2012-10-26 17:55:45mark.dickinsonsetrecipients: + mark.dickinson, benjamin.peterson, ezio.melotti, hieu.nguyen
2012-10-26 17:55:45mark.dickinsonsetmessageid: <>
2012-10-26 17:55:45mark.dickinsonlinkissue9192 messages
2012-10-26 17:55:45mark.dickinsoncreate