Skip to content

Commit de53bf4

Browse files
[3.14] gh-143089: Fix ParamSpec default examples to use list instead of tuple (GH-143179) (#143538)
Co-authored-by: VanshAgarwal24036 <[email protected]>
1 parent e8ac427 commit de53bf4

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
@@ -1450,13 +1450,13 @@ The following syntax creates a parameter specification that defaults\n\
14501450
to a callable accepting two positional-only arguments of types int\n\
14511451
and str:\n\
14521452
\n\
1453-
type IntFuncDefault[**P = (int, str)] = Callable[P, int]\n\
1453+
type IntFuncDefault[**P = [int, str]] = Callable[P, int]\n\
14541454
\n\
14551455
For compatibility with Python 3.11 and earlier, ParamSpec objects\n\
14561456
can also be created as follows::\n\
14571457
\n\
14581458
P = ParamSpec('P')\n\
1459-
DefaultP = ParamSpec('DefaultP', default=(int, str))\n\
1459+
DefaultP = ParamSpec('DefaultP', default=[int, str])\n\
14601460
\n\
14611461
Parameter specification variables exist primarily for the benefit of\n\
14621462
static type checkers. They are used to forward the parameter types of\n\

0 commit comments

Comments
 (0)