Closed GoogleCodeExporter closed 9 years ago
It's interesting, but I don't see it as an issue for bitstring, it's just
because there's a many to one mapping of bitstrings to floats, which isn't
anything I can affect...
Both bitstrings evaluate to 'nan' as a float, and as the conversion goes via a
float there's no way to keep the information as to which bitstring created the
float to start with.
'nan's are strange things, and the multiplicity of interpretations is most
easily shown with the lines:
>>> a = float('nan')
>>> a == a
False
Closing the bug as there's nothing I could ever do to save that bit - we're at
the mercy of the floating point interpretation in Python.
Original comment by dr.scott...@gmail.com
on 26 Nov 2013 at 12:14
Original issue reported on code.google.com by
944725BB...@gmail.com
on 25 Nov 2013 at 7:48