[Python-3000] Changing function-related TypeErrors
Guido van Rossum
guido at python.org
Tue May 9 22:49:25 CEST 2006
I'm not implying anything about Winter (whom I actually respect)
except that I don't see the merit of his proposal, and that I don't
see the value of more argument on such a small issue.
And why are you hiding behind an alias?
On 5/9/06, joe user <signspointtoprobably at yahoo.com> wrote:
> Does this mean you have no more actual technical reasons to oppose this
> change, but are just stomping your foot and implying bad things about
> Winter? Because there are people who agree with him, and I haven't seen any
> really compelling reasons to avoid this ten-line modification.
> Seriously, are you just dodging this issue?
> >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,
> >> > > 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/)
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
> countries) for 2¢/min or less.
> Python-3000 mailing list
> Python-3000 at python.org
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-3000