Skip> A shortcoming in int() hardly seems like a good reason to mess Skip> with str().
Gareth> How's it a shortcoming in int() that it doesn't do anything Gareth> with, say, int(2.345,19)?
My reasoning was that just because int() was written to ignore the second arg depending on type (the "shortcoming") doesn't mean that str() should as well.
"ignore" is perhaps the wrong word:
Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: int() can't convert non-string with explicit base