Comment 3 for bug 702933

I had forgotten the detail over where the string->integer conversion occurred, but I was pretty sure that was the reason for the check.

Checking for __int__ looks like a good replacement. Does it handle the case you are interested in?