Skip to content

Commit 5af09f5

Browse files
[3.13] gh-143089: Fix ParamSpec default examples to use list instead of tuple (GH-143179) (#143539)
Co-authored-by: VanshAgarwal24036 <148854295+VanshAgarwal24036@users.noreply.github.com>
1 parent e1572ea commit 5af09f5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Objects/typevarobject.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1175,13 +1175,13 @@ The following syntax creates a parameter specification that defaults\n\
11751175
to a callable accepting two positional-only arguments of types int\n\
11761176
and str:\n\
11771177
\n\
1178-
type IntFuncDefault[**P = (int, str)] = Callable[P, int]\n\
1178+
type IntFuncDefault[**P = [int, str]] = Callable[P, int]\n\
11791179
\n\
11801180
For compatibility with Python 3.11 and earlier, ParamSpec objects\n\
11811181
can also be created as follows::\n\
11821182
\n\
11831183
P = ParamSpec('P')\n\
1184-
DefaultP = ParamSpec('DefaultP', default=(int, str))\n\
1184+
DefaultP = ParamSpec('DefaultP', default=[int, str])\n\
11851185
\n\
11861186
Parameter specification variables exist primarily for the benefit of\n\
11871187
static type checkers. They are used to forward the parameter types of\n\

0 commit comments

Comments
 (0)