PEP 622: Remove type and complex from special cases (#1475)

This commit is contained in:
Brandt Bucher 2020-06-27 12:22:24 -07:00 committed by GitHub
parent 4b5513942c
commit 0146bb56f9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

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