TD22057 added the comment:
Is there any chance this will ever get fixed? Patches have been available for
5 years with no progress.
--
___
Python tracker
<https://bugs.python.org/issue9
Changes by TD22057 :
--
nosy: +TD22057
___
Python tracker
<http://bugs.python.org/issue9338>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
TD22057 <[EMAIL PROTECTED]> added the comment:
Martin is correct. I expected (naively) that struct would zero pad the
digits beyond the significant digits of a float. As to whether it's
exact or not, see my first message:
>>> v=1.8183e-7
>>> v
1.81830001e
TD22057 <[EMAIL PROTECTED]> added the comment:
I'm receiving a 32 bit floating point number encoded in binary format.
The correct value for that number is 1.8183e-7 which can be expressed in
single precision just fine. Given that the number in the binary
encoding is 1.8183e-7, I
TD22057 <[EMAIL PROTECTED]> added the comment:
That's not my code - it's an example ;)
My code reads binary data from a hardware system that is encoding 32 bit
floats. The numbers I get back from struct.decode have garbage appended
on the end of the floating point numbers b
New submission from TD22057 <[EMAIL PROTECTED]>:
FYI Actual version is 2.5.2 running on Linux RHE4.
>>> import struct
>>> fmt ='>f'
>>> v=1.8183e-7
>>> v
1.81830001e-07
>>> s=struct.pack(fmt,v)
>>> struct.u
