Fix markup bug in PEP 544
This commit is contained in:
parent
9012ec6e8c
commit
5af613bbb2
|
@ -752,7 +752,7 @@ However, it should be possible for protocol types to implement custom
|
||||||
instance and class checks when this makes sense, similar to how ``Iterable``
|
instance and class checks when this makes sense, similar to how ``Iterable``
|
||||||
and other ABCs in ``collections.abc`` and ``typing`` already do it,
|
and other ABCs in ``collections.abc`` and ``typing`` already do it,
|
||||||
but this is limited to non-generic and unsubscripted generic protocols
|
but this is limited to non-generic and unsubscripted generic protocols
|
||||||
(``Iterable`` is statically equivalent to ``Iterable[Any]`).
|
(``Iterable`` is statically equivalent to ``Iterable[Any]``).
|
||||||
The ``typing`` module will define a special ``@runtime`` class decorator
|
The ``typing`` module will define a special ``@runtime`` class decorator
|
||||||
that provides the same semantics for class and instance checks as for
|
that provides the same semantics for class and instance checks as for
|
||||||
``collections.abc`` classes, essentially making them "runtime protocols"::
|
``collections.abc`` classes, essentially making them "runtime protocols"::
|
||||||
|
|
Loading…
Reference in New Issue