From: <bc...@wo...> - 2002-01-11 13:18:00
|
On Thu, 10 Jan 2002 19:49:45 -0500, you wrote: [Paul Prescod wrote] > Is that a problem? If the user specifies an encoding then you could > decode. If they don't, I would suggest to just do a no-op. Under what > circumstances would the current exception be more helpful? [Brian Quinlan] > Because you are specifically looking for the exception to see if the > string can be converted to a Unicode object using the default encoding? No, it's because you can change the codec used to something more usefull than the default "ascii". [dman] >Is it supposed to be an error when trying to convert a unicode object >to a unicode object? I don't think so. And I agree. Passing a unicode object to unicode() should have been a no-op. Jython only has this 'problem' because we can't have different execution paths based on the type of string objects. regards, finn |