[Python-Dev] TypeError messages

Antoine Pitrou solipsis at pitrou.net
Sat Feb 21 18:12:37 CET 2015


On Sat, 21 Feb 2015 10:57:49 -0500
"R. David Murray" <rdmurray at bitdance.com> wrote:
> On Sun, 22 Feb 2015 00:26:23 +1000, Nick Coghlan <ncoghlan at gmail.com> wrote:
> > On 21 February 2015 at 00:05, Brett Cannon <brett at python.org> wrote:
> > >  I agree that type names don't need to be quoted.
> > 
> > As a user, I actually appreciate the quotes, because they make the
> > error pattern easier for me to parse. Compare:
> > 
> >     int expected, but found str
> >     float expected, but found int
> > 
> >     'int' expected, but found 'str'
> >     'float' expected, but found 'int'
> 
> It's not a big deal to me either way, but I find the version with the
> quotes makes me think it is looking for the literal string 'int', but
> found the literal string 'str', whereas in the first case it seems
> clear it is looking for objects of that type.  Perhaps this is just
> because I am used to the existing messages, but I think it goes
> beyond that.

Agreed.

Regards

Antoine.




More information about the Python-Dev mailing list