Forgetting "()" when calling methods

[Michael Hudson]

Tim Peters <tim.one at comcast.net> writes:

> [comparison stuff]
>
> No, the current state makes no sense.  In very early Pythons, it wasn't
> *possible* (for technical reasons) for a comparison to raise an exception
> (well, it could, but it got silently ignored).  When it became possible for
> comparisons to raise exceptions, new types started doing so, but
> pre-existing types generally didn't.

There was also the issue that before rich comparisons there was no way
for a type to know whether it was supposed to be testing equality or
order... having 2 != "42" raise an exception *would* cause anguish.
The time machine broke badly on this one.

Cheers,
M.

-- 
93. When someone says "I want a programming language in which I
    need only say what I wish done," give him a lollipop.
  -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html