Message20897
Logged In: YES
user_id=22785
Yes, it does look like lookup('') is fixed in CVS. So the
question is whether lookup() of something that isn't
convertable in the current encoding to a char* should raise a
LookupError. I can live with it not, though if it did, it would
make it a bit easier to determine if an arbitrary unicode string
is a name of a supported encoding.
I'm willing to put together a patch to raise LookupError if
that's what the behavior should be |
|
Date |
User |
Action |
Args |
2007-08-23 14:21:52 | admin | link | issue960874 messages |
2007-08-23 14:21:52 | admin | create | |
|