[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-08 Thread Benjamin Peterson
Benjamin Peterson added the comment: Done in r69438. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-08 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Could we remove __str__ and just stick with __repr__? Yes, I think it's the best thing to do. ___ Python tracker ___ _

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-08 Thread Benjamin Peterson
Benjamin Peterson added the comment: What sort of thing should str() on a memoryview return? Latin-1 decoded bytes? Could we remove __str__ and just stick with __repr__? -- nosy: +benjamin.peterson ___ Python tracker

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-08 Thread Hagen Fürstenau
Changes by Hagen Fürstenau : -- nosy: +hagen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-08 Thread Ezio Melotti
Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-07 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue5182] str() on memoryview of bytearray failing on py3k

2009-02-07 Thread Mark Hammond
New submission from Mark Hammond : % py30 -c "str(memoryview(bytearray((1,2,3" Traceback (most recent call last): File "", line 1, in TypeError: __str__ returned non-string (type bytes) The expected behaviour is that a string representation be returned. -- messages: 81363 nosy: m