66msgstr ""
77"Project-Id-Version : Python 3.13\n "
88"Report-Msgid-Bugs-To : \n "
9- "POT-Creation-Date : 2024-09-30 09:19 +0000\n "
9+ "POT-Creation-Date : 2024-11-11 06:16 +0000\n "
1010"PO-Revision-Date : 2024-07-11 11:12+0800\n "
1111"
Last-Translator :
Li-Hung Wang <[email protected] >\n "
1212"Language-Team : Chinese - TAIWAN (https://github.com/python/python-docs-zh- "
@@ -2788,13 +2788,14 @@ msgstr ""
27882788
27892789#: ../../library/typing.rst:1729
27902790msgid ""
2791- "This syntax can also be used to create bound and constrained type variables::"
2791+ "This syntax can also be used to create bounded and constrained type "
2792+ "variables::"
27922793msgstr ""
27932794
27942795#: ../../library/typing.rst:1732
27952796msgid ""
2796- "class StrSequence[S: str]: # S is a TypeVar bound to str\n"
2797- " ...\n"
2797+ "class StrSequence[S: str]: # S is a TypeVar with a ` str` upper bound; \n"
2798+ " ... # we can say that S is \" bounded by `str` \" \n"
27982799"\n"
27992800"\n"
28002801"class StrOrBytesSequence[A: (str, bytes)]: # A is a TypeVar constrained to "
@@ -2843,8 +2844,8 @@ msgstr ""
28432844
28442845#: ../../library/typing.rst:1766
28452846msgid ""
2846- "Note that type variables can be *bound *, *constrained*, or neither, but "
2847- "cannot be both bound *and* constrained."
2847+ "Note that type variables can be *bounded *, *constrained*, or neither, but "
2848+ "cannot be both bounded *and* constrained."
28482849msgstr ""
28492850
28502851#: ../../library/typing.rst:1769
@@ -2859,9 +2860,9 @@ msgstr ""
28592860
28602861#: ../../library/typing.rst:1777
28612862msgid ""
2862- "Bound type variables and constrained type variables have different semantics "
2863- "in several important ways. Using a *bound * type variable means that the "
2864- "``TypeVar`` will be solved using the most specific type possible::"
2863+ "Bounded type variables and constrained type variables have different "
2864+ "semantics in several important ways. Using a *bounded * type variable means "
2865+ "that the ``TypeVar`` will be solved using the most specific type possible::"
28652866msgstr ""
28662867
28672868#: ../../library/typing.rst:1781
@@ -2880,8 +2881,8 @@ msgstr ""
28802881
28812882#: ../../library/typing.rst:1792
28822883msgid ""
2883- "Type variables can be bound to concrete types , abstract types (ABCs or "
2884- "protocols ), and even unions of types::"
2884+ "The upper bound of a type variable can be a concrete type , abstract type "
2885+ "(ABC or Protocol ), or even a union of types::"
28852886msgstr ""
28862887
28872888#: ../../library/typing.rst:1795
@@ -2936,7 +2937,7 @@ msgid ""
29362937msgstr ""
29372938
29382939#: ../../library/typing.rst:1837
2939- msgid "The bound of the type variable, if any."
2940+ msgid "The upper bound of the type variable, if any."
29402941msgstr ""
29412942
29422943#: ../../library/typing.rst:1841
@@ -3249,8 +3250,8 @@ msgstr ""
32493250#: ../../library/typing.rst:2062
32503251msgid ""
32513252"Without ``ParamSpec``, the simplest way to annotate this previously was to "
3252- "use a :class:`TypeVar` with bound ``Callable[..., Any]``. However this "
3253- "causes two problems:"
3253+ "use a :class:`TypeVar` with upper bound ``Callable[..., Any]``. However "
3254+ "this causes two problems:"
32543255msgstr ""
32553256
32563257#: ../../library/typing.rst:2066
0 commit comments