Message173867
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:45 | mark.dickinson | set | recipients:
+ mark.dickinson, benjamin.peterson, ezio.melotti, hieu.nguyen |
2012-10-26 17:55:45 | mark.dickinson | set | messageid: <1351274145.34.0.28744257428.issue9192@psf.upfronthosting.co.za> |
2012-10-26 17:55:45 | mark.dickinson | link | issue9192 messages |
2012-10-26 17:55:45 | mark.dickinson | create | |
|