Calin Culianu added the comment:
Ok, Guido, thanks. Fair enough.
So regardless: what is the problem exactly if a C function expects an int but
gets given a float? Why does such strictness matter, in that it required a
whole other set of __index__ etc to be added? I am having trouble seeing
Calin Culianu added the comment:
Ok, well I found this in that issue you linked to:
This is the original "problem":
```
type __mul__ is wierd:
>> 'a'.__mul__(3.4)
'aaa'
>>> [1].__mul__(3.4)
[1, 1, 1]
```
And this is Guido's response:
>
Calin Culianu added the comment:
Hi, I'm cculianu, the reporting user.
May I get a link or some background for the motivation for this change? It
seems to me that there are vague allusions to "Decimal -> int cause problems in
past", or some such, and I'd like to read
