Byte warning mode and b'' != ''

[tiran]

BPO	3988
Nosy	@warsaw, @brettcannon, @pitrou, @vstinner, @tiran, @benjaminp
Files	bytes_ne_warning-3.patch: Raise a warning on b'' != '' and bytearray(b'') != ''

^{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 = 'https://github.com/warsaw'
closed_at = <Date 2008-10-17.01:51:12.815>
created_at = <Date 2008-09-28.11:32:56.051>
labels = ['interpreter-core', 'type-bug', 'release-blocker']
title = "Byte warning mode and b'' != ''"
updated_at = <Date 2008-10-17.01:51:12.814>
user = 'https://github.com/tiran'

bugs.python.org fields:

activity = <Date 2008-10-17.01:51:12.814>
actor = 'barry'
assignee = 'barry'
closed = True
closed_date = <Date 2008-10-17.01:51:12.815>
closer = 'barry'
components = ['Interpreter Core']
creation = <Date 2008-09-28.11:32:56.051>
creator = 'christian.heimes'
dependencies = []
files = ['11798']
hgrepos = []
issue_num = 3988
keywords = ['patch']
message_count = 12.0
messages = ['73969', '73973', '73979', '73984', '73985', '73986', '73989', '73990', '73991', '74063', '74782', '74891']
nosy_count = 6.0
nosy_names = ['barry', 'brett.cannon', 'pitrou', 'vstinner', 'christian.heimes', 'benjamin.peterson']
pr_nums = []
priority = 'release blocker'
resolution = None
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue3988'
versions = ['Python 3.0']

[tiran]

In byte warning mode (-b or -bb command line argument) b'' == '' raises
an exception but b'' != '' doesn't.

./python -bb
>>> b'' == ''
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
BytesWarning: Comparison between bytes and string
>>> b'' != ''
True

I can't recall why I implemented the byte warning mode this way. But
nowadays I think it could hide bugs in code like "while egg != ''" where
egg is a byte instance.

[benjaminp]

+1

I was just confused by this fact yesterday. :)

[pitrou]

+1 as well. Lib/pty.py had a line like that ("while buf != ''") and I
wondered why no exception was thrown with -bb while the variable was a
bytes object.

[vstinner]

Here is a patch for this issue.

[tiran]

Thanks for the patch but you've missed a spot in bytearrayobject.c:

Objects/bytearrayobject.c: if (Py_BytesWarningFlag && op == Py_EQ) {
Objects/bytesobject.c: if (Py_BytesWarningFlag && (op == Py_EQ) &&

[benjaminp]

It would also be nice to have tests. (in test_bytes)

[vstinner]

@christian.heimes: Oops, i totally forget the bytearray() type. Here
is a new patch.

[vstinner]

I don't know how to activate BytesWarning as error (as "python3 -bb"
does). Here is an patch for tests only working with "python3 -bb".

[benjaminp]

warnings.simplefilter("always", BytesWarning) should do the trick.

[brettcannon]

Setting as a deferred blocker since this is a 3.0 thing and not a 2.6 thing.

[vstinner]

New patch including the test. The test doesn't fail anymore if -bb is
not set (test is just ignored). See also issue bpo-4125 (force -bb option
for runtests.sh).

[warsaw]

r66950