PEP 622: Remove type and complex from special cases (#1475)
This commit is contained in:
parent
4b5513942c
commit
0146bb56f9
|
@ -603,10 +603,10 @@ The procedure is as following:
|
||||||
Such a protocol favors simplicity of implementation over flexibility and
|
Such a protocol favors simplicity of implementation over flexibility and
|
||||||
performance. For other considered alternatives, see `rejected ideas`_.
|
performance. For other considered alternatives, see `rejected ideas`_.
|
||||||
|
|
||||||
For the most commonly-matched built-in types (specifically: ``bool``,
|
For the most commonly-matched built-in types (``bool``,
|
||||||
``bytearray``, ``bytes``, ``complex``, ``dict``, ``float``,
|
``bytearray``, ``bytes``, ``dict``, ``float``,
|
||||||
``frozenset``, ``int``, ``list``, ``set``, ``str``, ``tuple``, and
|
``frozenset``, ``int``, ``list``, ``set``, ``str``, and ``tuple``), a
|
||||||
``type``), a single positional sub-pattern is allowed to be passed to
|
single positional sub-pattern is allowed to be passed to
|
||||||
the call. Rather than being matched against any particular attribute
|
the call. Rather than being matched against any particular attribute
|
||||||
on the proxy, it is instead matched against the proxy itself. This
|
on the proxy, it is instead matched against the proxy itself. This
|
||||||
creates behavior that is useful and intuitive for these objects:
|
creates behavior that is useful and intuitive for these objects:
|
||||||
|
|
Loading…
Reference in New Issue