On May 21, 3:41 pm, "Chris Mellon" <[EMAIL PROTECTED]> wrote: > When told why you got different results (an answer you > probably already knew, if you know enough about IEEE to do the > auto-conversion you alluded to) ...
Of course I know a lot about IEEE, but you are assuming that I also know a lot about Python, which I don't. I assumed Python was doing the auto-conversion, too, because I had heard that Python supported arbitrary precision math. Jerry Hill explained that you had to load a separate package to do it. > you treated it as another opportunity > to (not very subtly) imply that Python was doing the wrong thing. This person who started this thread posted the calculations showing that Python was doing the wrong thing, and filed a bug report on it. If someone pointed out a similar problem in Flaming Thunder, I would agree that Flaming Thunder was doing the wrong thing. I would fix the problem a lot faster, though, within hours if possible. Apparently this particular bug has been lurking on Bugzilla since 2003: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323 -- http://mail.python.org/mailman/listinfo/python-list
