Message75915
The left operand is a bytestring and the right operand is a unicode
string, so it makes sense that it raises an exception, although it would
be clearer if it said "'in <string>' requires unicode string as left
operand".
I agree that if it's going to do implicit decoding so that it'll accept
'f' in u'foo' then it should probably raise a UnicodeDecodeError when
that fails.
If it's reporting a /TypeError/ then it should also reject 'f' in u'foo'. |
|
Date |
User |
Action |
Args |
2008-11-15 17:37:46 | mrabarnett | set | recipients:
+ mrabarnett, ezio.melotti |
2008-11-15 17:37:46 | mrabarnett | set | messageid: <1226770666.07.0.601144946755.issue4328@psf.upfronthosting.co.za> |
2008-11-15 17:37:45 | mrabarnett | link | issue4328 messages |
2008-11-15 17:37:44 | mrabarnett | create | |
|