Hi,

I found that unlike the string object, the replace()
method in the unicode object doesn't throw an exception
when you supply an empty pattern string. Instead it
slaps on the replace string a few times at the end. 

I'm supplying a patch to make the unicode object behave
like the string object.

I realize that in 2.3, doing replace() with an empty
pattern string will work differently so maybe you don't
consider throwing an exception the Right Way(TM), but
I'm presenting it to you in case you (like me) thinks
it's just better if unicode and string objects behave
in the same way while not changing the way that string
objects currently work in 2.2.

Best regards,
Fredrik Juhlin