[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

Barry A. Warsaw added the comment: Since we do not yet have a patch for this, I'm knocking it off the list for 2.6.3. It seems like an annoying loss of compatibility, but do we have any reports of it breaking real-world code? -- nosy: +barry priority: release blocker -> high _

[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

Changes by Georg Brandl : -- priority: high -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

Antoine Pitrou added the comment: Looks like a potentially annoying bug to me. -- nosy: +pitrou priority: -> high stage: -> needs patch versions: +Python 2.7 ___ Python tracker ___

[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

Jean-Paul Calderone added the comment: Perhaps also worth noting is that in Python 2.4 as well, str(exception) and unicode(exception) returned the same thing. Unlike some other exception changes in 2.6, this doesn't seem to be a return to older behavior, but just a new behavior. (Or maybe no o

[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6108] unicode(exception) behaves differently on Py2.6 when len(exception.args) > 1

New submission from Ezio Melotti : On Python 2.5 str(exception) and unicode(exception) return the same text: >>> err UnicodeDecodeError('ascii', '\xc3\xa0', 0, 1, 'ordinal not in range(128)') >>> str(err) "'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128)" >>> unicode(