iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 622: Clarify the status of True, False and None as literals

This commit is contained in:
Guido van Rossum 2020-06-24 17:06:42 -07:00
parent 1560745bdc
commit 8f43d3ef64
1 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-0622.rst
View File

@ -215,7 +215,7 @@ Literal Pattern
~~~~~~~~~~~~~~~
A literal pattern consists of a simple literal like a string, a number,
a boolean, or ``None``::
a Boolean literal (``True`` or ``False``), or ``None``::
match number:
case 0:
@ -237,6 +237,16 @@ literals for the purpose of pattern matching. Unary plus is not allowed.
Binary plus and minus are allowed only to join a real number and an imaginary
number to form a complex number, such as ``1+1j``.
Note that because equality (``__eq__``) is used, and the equivalency
between Booleans and the integers ``0`` and ``1``, there is no
practical difference between the following two::
case True:
...
case 1:
...
Triple-quoted strings are supported. Raw strings and byte strings
are supported. F-strings are not allowed (since in general they are not
really literals).
@ -284,6 +294,8 @@ Note: one can still match on a collection with equal items using `guards`_.
Also, ``[x, y] | Point(x, y)`` is a legal pattern because the two
alternatives are never matched at the same time.
Also note that ``None``, ``False`` and ``True`` are literals, not names.
.. _constant_value_pattern: