str(bytes) does __repr__() instead of __str__()

[jwezel]

BPO	26151
Nosy	@doerwalter, @ezio-melotti, @vadmium, @eryksun

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-01-19.12:33:43.188>
created_at = <Date 2016-01-19.11:52:03.890>
labels = ['interpreter-core', 'type-bug', 'invalid', 'expert-unicode']
title = 'str(bytes) does __repr__() instead of __str__()'
updated_at = <Date 2016-01-19.21:58:17.946>
user = 'https://bugs.python.org/jwezel'

bugs.python.org fields:

activity = <Date 2016-01-19.21:58:17.946>
actor = 'jwezel'
assignee = 'none'
closed = True
closed_date = <Date 2016-01-19.12:33:43.188>
closer = 'vstinner'
components = ['Interpreter Core', 'Unicode']
creation = <Date 2016-01-19.11:52:03.890>
creator = 'jwezel'
dependencies = []
files = []
hgrepos = []
issue_num = 26151
keywords = []
message_count = 10.0
messages = ['258583', '258588', '258589', '258603', '258604', '258606', '258608', '258610', '258620', '258625']
nosy_count = 5.0
nosy_names = ['doerwalter', 'ezio.melotti', 'martin.panter', 'eryksun', 'jwezel']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26151'
versions = ['Python 3.4']

[jwezel]

str(b'xxx') returns "b'xxx'" instead of 'xxx'

[vstinner]

Yes. It's a feature, not a bug. You muse decode manually bytes to get type: b'xxx'.decode('ascii') or str(b'xxx'.decode('ascii')).

[jwezel]

Bad feature, as it is a violation of POLA.

[eryksun]

Bad feature, as it is a violation of POLA.

I would be astonished if the default __str__ conversion returned a Latin-1 decoding, which won't fail, or used the locale encoding or UTF-8, which could fail. The more explicit call x.decode() uses UTF-8 as the default encoding.

[jwezel]

Who's talking about latin-1 in Python3? Of course str() needs to return decode('utf-8').

[doerwalter]

Who's talking about latin-1 in Python3? Of course str() needs to return decode('utf-8').

So that would mean that:

   print(b"\xff")

will always fail!

[jwezel]

The other question is why one would want to run such a statement. This is almost certainly a bug in which case an error one would be better off with an exception.

[doerwalter]

But this leads to uninspectable objects.

[vadmium]

A warning is already emitted if you enable it with the “-b” flag, which I recommend. You can even turn the warning into an error with “-bb”. And you can always use repr() or ascii() to inspect for a more robust inspection.

$ python3 -bb
Python 3.5.0 (default, Sep 20 2015, 11:28:25) 
[GCC 5.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print(b"\xFF")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
BytesWarning: str() on a bytes instance
>>> print(repr(b"\xFF"))
b'\xff'

[jwezel]

But this leads to uninspectable objects.

An inspection would be done with repr() which should not cause a problem.

Besides. the official and correct way of handling an ff character is to emit a Unicode replacement code, not to issue an exception. Another flaw in the whole story.