1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Apply 'mod' role to typing module (#133201)

Browse Source 
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
This commit is contained in:
Rafael Fontenelle 2025-04-30 13:52:03 -03:00 committed by GitHub
parent b451516aa6
commit 2b67db7ce3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Doc/library/typing.rst
View File

@ -665,7 +665,7 @@ through a simple assignment::
User-defined generics for parameter expressions are also supported via parameter User-defined generics for parameter expressions are also supported via parameter
specification variables in the form ``[**P]``. The behavior is consistent specification variables in the form ``[**P]``. The behavior is consistent
with type variables' described above as parameter specification variables are with type variables' described above as parameter specification variables are
treated by the typing module as a specialized type variable. The one exception treated by the :mod:`!typing` module as a specialized type variable. The one exception
to this is that a list of types can be used to substitute a :class:`ParamSpec`:: to this is that a list of types can be used to substitute a :class:`ParamSpec`::
>>> class Z[T, **P]: ... # T is a TypeVar; P is a ParamSpec >>> class Z[T, **P]: ... # T is a TypeVar; P is a ParamSpec
@ -706,7 +706,7 @@ are intended primarily for static type checking.
A user-defined generic class can have ABCs as base classes without a metaclass A user-defined generic class can have ABCs as base classes without a metaclass
conflict. Generic metaclasses are not supported. The outcome of parameterizing conflict. Generic metaclasses are not supported. The outcome of parameterizing
generics is cached, and most types in the typing module are :term:`hashable` and generics is cached, and most types in the :mod:`!typing` module are :term:`hashable` and
comparable for equality. comparable for equality.
@ -2787,7 +2787,7 @@ types.
Protocols Protocols
--------- ---------
The following protocols are provided by the typing module. All are decorated The following protocols are provided by the :mod:`!typing` module. All are decorated
with :func:`@runtime_checkable <runtime_checkable>`. with :func:`@runtime_checkable <runtime_checkable>`.
.. class:: SupportsAbs .. class:: SupportsAbs
@ -3531,7 +3531,7 @@ Deprecated aliases
------------------ ------------------
This module defines several deprecated aliases to pre-existing This module defines several deprecated aliases to pre-existing
standard library classes. These were originally included in the typing standard library classes. These were originally included in the :mod:`!typing`
module in order to support parameterizing these generic classes using ``[]``. module in order to support parameterizing these generic classes using ``[]``.
However, the aliases became redundant in Python 3.9 when the However, the aliases became redundant in Python 3.9 when the
corresponding pre-existing classes were enhanced to support ``[]`` (see corresponding pre-existing classes were enhanced to support ``[]`` (see
@ -3544,7 +3544,7 @@ interpreter for these aliases.
If at some point it is decided to remove these deprecated aliases, a If at some point it is decided to remove these deprecated aliases, a
deprecation warning will be issued by the interpreter for at least two releases deprecation warning will be issued by the interpreter for at least two releases
prior to removal. The aliases are guaranteed to remain in the typing module prior to removal. The aliases are guaranteed to remain in the :mod:`!typing` module
without deprecation warnings until at least Python 3.14. without deprecation warnings until at least Python 3.14.
Type checkers are encouraged to flag uses of the deprecated types if the Type checkers are encouraged to flag uses of the deprecated types if the