On Thu, Sep 09, 2004 at 03:11:51PM -0400, Tim Peters wrote: > '%s' is documented as "String (converts any python object using > str())". It's str(A()) that raises the exception you're seeing, > not interpolation. Shouldn't '%s' % u'\u1234' also raise an exception then? > To worm around that, you'll effectively have to duplicate > PyObject_Str's implementation Yes. I want something like "PyObject_UnicodeOrStr" that would return either a unicode object or a str object. That would make it easier to write code that produces 'str' results if unicode characters don't appear in any of the inputs. Having __str__ methods that can return either 'unicode' or 'str' objects is also very handy (I don't see how you can say that it doesn't make any sense). Perhaps I am on the wrong track. However, if I understand the /F bot correctly, he favours a design that does not force everthing to unicode strings. Neil
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4