Comment 1 for bug 1044198

I changed the title and removed the "crash" statement. All I get is a simple ValueError with the normal error handling kicking in. The same happens for a number of other converters when presented with invalid input.

I'm not sure I'd change anything here at all. But I'd prefer an explicit exception over some guessing or partial data conversion.