All commit authors signed the Contributor License Agreement.

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

Most changes to Python require a NEWS entry.

Please add it using the blurb_it web app or the blurb command-line tool.

I doubt this needs a news entry.

I don't think this change should be made. "This thing is not false" is an English description, not a Python expression. This is the same as the docstring of these methods.

I think capitalizing suggests that these methods do if expr is not False: fail() and if expr is not True: fail(), which is incorrect; what they actually do are if expr: fail() and if not expr: fail().

As Dennis noted, the wording is correct as-is. We use True and False for the exact boolean objects. We use true and false for any object treated as true or false during branching. For example, the number 15 is a true value but is not the object True.

>>> x = 15
>>> if x:
...     print(x, 'treated as true for branching purposes')
... 
15 treated as true for branching purposes

>>> x is True
False