Message 144138 - Python tracker

Message144138

Author	skrah
Recipients	mark.dickinson, meador.inge, skrah
Date	2011-09-16.16:56:04
SpamBayes Score	0.00063011463
Marked as misclassified	No
Message-id	<20110916165304.GA19605@sleipnir.bytereef.org>
In-reply-to	<CAK1QooqQuM8CnW++zTjQmGYxFR4Oe2qWAA285rC__oOP-F2YDw@mail.gmail.com>

Content
Meador Inge <report@bugs.python.org> wrote: > The behavior around '__int__' in previous versions seems somewhat accidental. I think struct followed the functions in longobject.c, which is not really consistent with respect to duck typing. See also #12965 or http://bugs.python.org/issue1172711#msg48086. But I think that the decision to accept __index__() for both signed and unsigned integer formats is good for consistency. For 'P' I'm not sure, but course it might be used in the wild by now.

Content

Meador Inge <report@bugs.python.org> wrote:
> The behavior around '__int__' in previous versions seems somewhat accidental.

I think struct followed the functions in longobject.c, which is not
really consistent with respect to duck typing. See also #12965 or
http://bugs.python.org/issue1172711#msg48086.

But I think that the decision to accept __index__() for both signed
and unsigned integer formats is good for consistency.

For 'P' I'm not sure, but course it might be used in the wild by now.

History
Date	User	Action	Args
2011-09-16 16:56:06	skrah	set	recipients: + skrah, mark.dickinson, meador.inge
2011-09-16 16:56:05	skrah	link	issue12974 messages
2011-09-16 16:56:05	skrah	create