"Terry Reedy" <[EMAIL PROTECTED]> writes:
> "Tim Peters" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > [Donn Cave]
> >> I ran into a phenomenon that seemed odd to me, while testing a
> >> build of Python 2.4.1 on BeOS 5.04, on PowerPC 603e.
> >>
> >> test_builtin.py, for examp
"Tim Peters" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> [Donn Cave]
>> I ran into a phenomenon that seemed odd to me, while testing a
>> build of Python 2.4.1 on BeOS 5.04, on PowerPC 603e.
>>
>> test_builtin.py, for example, fails a couple of tests with errors
>> claiming that
[Donn Cave]
> I ran into a phenomenon that seemed odd to me, while testing a
> build of Python 2.4.1 on BeOS 5.04, on PowerPC 603e.
>
> test_builtin.py, for example, fails a couple of tests with errors
> claiming that apparently identical floating point values aren't equal.
> But it only does that
Donn Cave wrote:
> I ran into a phenomenon that seemed odd to me, while testing a
> build of Python 2.4.1 on BeOS 5.04, on PowerPC 603e.
>
> test_builtin.py, for example, fails a couple of tests with errors
> claiming that apparently identical floating point values aren't equal.
> But it only does
I ran into a phenomenon that seemed odd to me, while testing a
build of Python 2.4.1 on BeOS 5.04, on PowerPC 603e.
test_builtin.py, for example, fails a couple of tests with errors
claiming that apparently identical floating point values aren't equal.
But it only does that when imported, and only
