From 67d3d0344f129d486540ab0a41c8c820ca835d18 Mon Sep 17 00:00:00 2001
From: VanshAgarwal24036 <148854295+VanshAgarwal24036@users.noreply.github.com>
Date: Thu, 8 Jan 2026 09:02:44 +0530
Subject: [PATCH] gh-143089: Fix ParamSpec default examples to use list instead
 of tuple (#143179)

---
 Objects/typevarobject.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Objects/typevarobject.c b/Objects/typevarobject.c
index 8e43962c7e37..2ec546aff52c 100644
--- a/Objects/typevarobject.c
+++ b/Objects/typevarobject.c
@@ -1451,13 +1451,13 @@ The following syntax creates a parameter specification that defaults\n\
 to a callable accepting two positional-only arguments of types int\n\
 and str:\n\
 \n\
-    type IntFuncDefault[**P = (int, str)] = Callable[P, int]\n\
+    type IntFuncDefault[**P = [int, str]] = Callable[P, int]\n\
 \n\
 For compatibility with Python 3.11 and earlier, ParamSpec objects\n\
 can also be created as follows::\n\
 \n\
     P = ParamSpec('P')\n\
-    DefaultP = ParamSpec('DefaultP', default=(int, str))\n\
+    DefaultP = ParamSpec('DefaultP', default=[int, str])\n\
 \n\
 Parameter specification variables exist primarily for the benefit of\n\
 static type checkers.  They are used to forward the parameter types of\n\
-- 
2.47.3