[Python-3000] Changing function-related TypeErrors

[Guido van Rossum]

Can we just agree to disagree? Read the piece on python.org/dev about
knowing when to stop.

On 5/8/06, Collin Winter <collinw at gmail.com> wrote:
> On 5/7/06, Guido van Rossum <guido at python.org> wrote:
> > On 5/7/06, Collin Winter <collinw at gmail.com> wrote:
> > > This -- more intuitive error messages -- is really what I'm after, and
> > > while you may think of type of "def foo(a, b, c):..." as "a function
> > > with three required arguments", I'd wager that most Python
> > > programmers, if asked what type foo has, would say simply, "it's a
> > > function".
> >
> > Then introducing a new exception isn't going to make a difference.
>
> Sure it will: the name of the exception class is effectively part of
> the error message once the exception instance bubbles up to the user.
> "TypeError: foo() got an unexpected keyword argument 'bar'".
>
> Collin Winter
>


--
--Guido van Rossum (home page: http://www.python.org/~guido/)