mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-09-09 18:32:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

bpo-45346: Keep docs consistent regarding true and false values (GH-28697)

Browse source
This commit is contained in:
Raymond Hettinger 2021-10-02 13:48:08 -05:00 • committed by GitHub
parent 0742abdc48
commit db91b058d5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Doc/library/ast.rst
View file

@ -1266,7 +1266,7 @@ Pattern matching
the pattern matches the subject.
``body`` contains a list of nodes to execute if the pattern matches and
the result of evaluating the guard expression is truthy.
the result of evaluating the guard expression is true.
.. doctest::

8
Doc/reference/compound_stmts.rst
View file

@ -585,8 +585,8 @@ Here's an overview of the logical flow of a match statement:
#. If the pattern succeeds, the corresponding guard (if present) is evaluated. In
this case all name bindings are guaranteed to have happened.
* If the guard evaluates as truthy or missing, the ``block`` inside ``case_block`` is
executed.
* If the guard evaluates as true or is missing, the ``block`` inside
``case_block`` is executed.
* Otherwise, the next ``case_block`` is attempted as described above.
@ -637,10 +637,10 @@ The logical flow of a ``case`` block with a ``guard`` follows:
#. If the pattern succeeded, evaluate the ``guard``.
* If the ``guard`` condition evaluates to "truthy", the case block is
* If the ``guard`` condition evaluates as true, the case block is
selected.
* If the ``guard`` condition evaluates to "falsy", the case block is not
* If the ``guard`` condition evaluates as false, the case block is not
selected.
* If the ``guard`` raises an exception during evaluation, the exception

2
Lib/test/test_builtin.py
View file

@ -1861,7 +1861,7 @@ class BuiltinTest(unittest.TestCase):
# be evaluated in a boolean context (virtually all such use cases
# are a result of accidental misuse implementing rich comparison
# operations in terms of one another).
# For the time being, it will continue to evaluate as truthy, but
# For the time being, it will continue to evaluate as a true value, but
# issue a deprecation warning (with the eventual intent to make it
# a TypeError).
self.assertWarns(DeprecationWarning, bool, NotImplemented)