Can we just agree to disagree? Read the piece on python.org/dev about knowing when to stop.
On 5/8/06, Collin Winter <[EMAIL PROTECTED]> wrote: > On 5/7/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > On 5/7/06, Collin Winter <[EMAIL PROTECTED]> 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/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
