Craig McQueen added the comment: Another thing I discovered, for Example 1: 4. If test_object.__str__() returns a Unicode object (for some reason), and test_object.__unicode__() does not exist, then the Unicode value from the __str__() call is used as-is (no conversion to string, no encoding errors). This is also a little surprising [in this situation unicode(test_object) also returns the Unicode object returned by __str__() as-is, so I guess there's some consistency there]. ---------- _______________________________________ Python tracker http://bugs.python.org/issue9196 _______________________________________

Craig McQueen added the comment: I should be able to attach my test code. But it is at my work, and I'm on holidays for 2 more weeks. Sorry 'bout that! I do assume that Python 3 greatly simplifies this. ---------- _______________________________________ Python tracker http://bugs.python.org/issue9196 _______________________________________

Ezio Melotti added the comment: Python 3 checks the return types of __bytes__ and __str__, raising an error if it's not bytes and str respectively:

...

...

str(C()) TypeError: __str__ returned non-string (type bytes) bytes(C()) TypeError: __bytes__ returned non-bytes (type str)

The Python 2 doc for unicode() says[0]: """ For objects which provide a __unicode__() method, it will call this method without arguments to create a Unicode string. For all other objects, the 8-bit string version or representation is requested and then converted to a Unicode string using the codec for the default encoding in 'strict' mode. """ The doc for .__unicode__() says[1]: """ Called to implement unicode() built-in; should return a Unicode object. When this method is not defined, string conversion is attempted, and the result of string conversion is converted to Unicode using the system default encoding. """ This is consistent with unicode() doc (but it doesn't mention that 'strict' is used). It also says that the method *should* return unicode, but it can also returns a str that gets coerced by unicode(). The doc for .__str__() says[2]: """ Called by the str() built-in function and by the print statement to compute the “informal” string representation of an object. [...] The return value must be a string object. """ This is wrong because the return value can be unicode too (this has been changed at some point, it used to be true on older versions). That said, some of the behaviors described by Craig (e.g. __str__ that returns unicode) are not documented and documenting them might save some confusion. However these "weird" behaviors are most likely errors and the fact that there are no exception is just because Python 2 is not strict with str/unicode. I think a better way to solve the problem is to document clearly how these methods should be used (i.e. if __unicode__ should be preferred over __str__, if it's necessary to implement both, what they should return, etc.). [0]: http://docs.python.org/library/functions.html#unicode [1]: http://docs.python.org/reference/datamodel.html#object.__unicode__ [2]: http://docs.python.org/reference/datamodel.html#object.__str__ ---------- _______________________________________ Python tracker http://bugs.python.org/issue9196 _______________________________________

Éric Araujo added the comment: More info on this thread: http://mail.python.org/pipermail/python-dev/2006-December/070237.html ---------- _______________________________________ Python tracker http://bugs.python.org/issue9196 _______________________________________

Serhiy Storchaka added the comment: Python 2.7 is no longer supported. ---------- nosy: +serhiy.storchaka resolution: -> out of date stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker https://bugs.python.org/issue9196 _______________________________________