From d1ae6431c7896f595082e403f780c4441b2ea0df Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Tue, 30 Jun 2026 11:15:08 +0200 Subject: [PATCH] [3.13] gh-133510: Add links to more info for the match statement in FAQ anwser (GH-133511) (#152654) (cherry picked from commit 77181570da2d6d8f7bfca39f438ef0a893a30567) Co-authored-by: xzkdeng Co-authored-by: sobolevn Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Co-authored-by: Stan Ulbrych --- Doc/faq/design.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst index 73c670b0a138..3872a9ab9364 100644 --- a/Doc/faq/design.rst +++ b/Doc/faq/design.rst @@ -263,6 +263,8 @@ In general, structured switch statements execute one block of code when an expression has a particular value or set of values. Since Python 3.10 one can easily match literal values, or constants within a namespace, with a ``match ... case`` statement. +See :ref:`the specification ` and :ref:`the tutorial ` +for more information about :keyword:`match` statements. An older alternative is a sequence of ``if... elif... elif... else``. For cases where you need to choose from a very large number of possibilities, -- 2.47.3