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

Changes by Hagen Fürstenau hfuerste...@gmx.net: -- nosy: +hagen ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5182 ___ ___ Python-bugs-list

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

Benjamin Peterson benja...@python.org 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

Antoine Pitrou pit...@free.fr added the comment: Could we remove __str__ and just stick with __repr__? Yes, I think it's the best thing to do. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5182 ___

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

Benjamin Peterson benja...@python.org added the comment: Done in r69438. -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5182 ___

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

New submission from Mark Hammond mhamm...@users.sourceforge.net: % py30 -c str(memoryview(bytearray((1,2,3 Traceback (most recent call last): File string, line 1, in module TypeError: __str__ returned non-string (type bytes) The expected behaviour is that a string representation be

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

Changes by Antoine Pitrou pit...@free.fr: -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5182 ___ ___ Python-bugs-list mailing