From b6fb779489d1daf0c32684eb614c92446d8eacb1 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
<31488909+miss-islington@users.noreply.github.com>
Date: Mon, 29 Aug 2022 00:14:33 -0700
Subject: [PATCH] GH-96359: Fix docs that claim int(0|1) doesn't match False
(GH-96361)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
(cherry picked from commit 3d3a86ed40626471b2c9e7f1336b228eb0dd0879)
Co-authored-by: Jonathan Oberländer <github@l3vi.de>
---
Doc/reference/compound_stmts.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Doc/reference/compound_stmts.rst b/Doc/reference/compound_stmts.rst
index 2b429681e1a..911c38f7235 100644
--- a/Doc/reference/compound_stmts.rst
+++ b/Doc/reference/compound_stmts.rst
@@ -1074,7 +1074,7 @@ subject value:
These classes accept a single positional argument, and the pattern there is matched
against the whole object rather than an attribute. For example ``int(0|1)`` matches
- the value ``0``, but not the values ``0.0`` or ``False``.
+ the value ``0``, but not the value ``0.0``.
In simple terms ``CLS(P1, attr=P2)`` matches only if the following happens:
--
GitLab