Bug report
Bug description:
Related to: #103487
# literal.py
print(~False)
print(~True)
# var.py
a = True
print(~a)
b = False
print(~b)
A DeprecationWarning is reported for var.py, but not for literal.py.
$ python -c 'import sys; print(sys.version)'
3.15.0a0 (heads/main:42d03f3, May 19 2025, 23:32:01) [GCC 15.1.1 20250425 (Red Hat 15.1.1-1)]
$ python literal.py
-1
-2
$ python var.py
/tmp/scratch/var.py:2: DeprecationWarning: Bitwise inversion '~' on bool is deprecated and will be removed in Python 3.16. This returns the bitwise inversion of the underlying int object and is usually not what you expect from negating a bool. Use the 'not' operator for boolean negation or ~int(x) if you really want the bitwise inversion of the underlying int.
print(~a)
-2
/tmp/scratch/var.py:5: DeprecationWarning: Bitwise inversion '~' on bool is deprecated and will be removed in Python 3.16. This returns the bitwise inversion of the underlying int object and is usually not what you expect from negating a bool. Use the 'not' operator for boolean negation or ~int(x) if you really want the bitwise inversion of the underlying int.
print(~b)
-1
What's interesting is that there's a test for this:
|
with self.assertWarns(DeprecationWarning): |
|
# also check that the warning is issued in case of constant |
|
# folding at compile time |
|
self.assertEqual(eval("~False"), -1) |
and the DeprecationWarning
is raised if
eval("~True") is used instead of just
~True
$ python -c 'print(~True)'
-2
$ python -c 'print(eval("~True"))'
<string>:1: DeprecationWarning: Bitwise inversion '~' on bool is deprecated and will be removed in Python 3.16. This returns the bitwise inversion of the underlying int object and is usually not what you expect from negating a bool. Use the 'not' operator for boolean negation or ~int(x) if you really want the bitwise inversion of the underlying int.
-2
CPython versions tested on:
CPython main branch, 3.13
Operating systems tested on:
Linux
Linked PRs
Bug report
Bug description:
Related to: #103487
A DeprecationWarning is reported for
var.py, but not forliteral.py.What's interesting is that there's a test for this:
cpython/Lib/test/test_bool.py
Lines 68 to 71 in 42d03f3
eval("~True")is used instead of just~TrueCPython versions tested on:
CPython main branch, 3.13
Operating systems tested on:
Linux
Linked PRs