Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity
cpython/Lib/keyword.py

65 lines
1.0 KiB
Python
Raw Normal View History

bpo-40939: Generate keyword.py using the new parser (GH-20800)
2020-06-11 09:45:15 -03:00
"""Keywords (from "Grammar/python.gram")
More trivial comment -> docstring transformations by Ka-Ping Yee, who writes: Here is batch 2, as a big collection of CVS context diffs. Along with moving comments into docstrings, i've added a couple of missing docstrings and attempted to make sure more module docstrings begin with a one-line summary. I did not add docstrings to the methods in profile.py for fear of upsetting any careful optimizations there, though i did move class documentation into class docstrings. The convention i'm using is to leave credits/version/copyright type of stuff in # comments, and move the rest of the descriptive stuff about module usage into module docstrings. Hope this is okay.
2000-02-04 11:10:34 -04:00
This file is automatically generated; please don't muck it up!
To update the symbols in this file, 'cd' to the top directory of
bpo-36143: Regenerate Lib/keyword.py from the Grammar and Tokens file using pgen (GH-12456) Now that the parser generator is written in Python (Parser/pgen) we can make use of it to regenerate the Lib/keyword file that contains the language keywords instead of parsing the autogenerated grammar files. This also allows checking in the CI that the autogenerated files are up to date.
2019-03-25 19:01:12 -03:00
the python source tree and run:
bpo-40939: Generate keyword.py using the new parser (GH-20800)
2020-06-11 09:45:15 -03:00
PYTHONPATH=Tools/peg_generator python3 -m pegen.keywordgen \
Delete remaining references to Grammar/Grammar from docs (#21624) (Ironically, the file itself remains, see https://github.com/we-like-parsers/cpython/issues/135.)
2020-07-26 12:27:52 -03:00
Grammar/python.gram \
bpo-40939: Generate keyword.py using the new parser (GH-20800)
2020-06-11 09:45:15 -03:00
Grammar/Tokens \
Lib/keyword.py
More trivial comment -> docstring transformations by Ka-Ping Yee, who writes: Here is batch 2, as a big collection of CVS context diffs. Along with moving comments into docstrings, i've added a couple of missing docstrings and attempted to make sure more module docstrings begin with a one-line summary. I did not add docstrings to the methods in profile.py for fear of upsetting any careful optimizations there, though i did move class documentation into class docstrings. The convention i'm using is to leave credits/version/copyright type of stuff in # comments, and move the rest of the descriptive stuff about module usage into module docstrings. Hope this is okay.
2000-02-04 11:10:34 -04:00
bpo-36143: Regenerate Lib/keyword.py from the Grammar and Tokens file using pgen (GH-12456) Now that the parser generator is written in Python (Parser/pgen) we can make use of it to regenerate the Lib/keyword file that contains the language keywords instead of parsing the autogenerated grammar files. This also allows checking in the CI that the autogenerated files are up to date.
2019-03-25 19:01:12 -03:00
Alternatively, you can run 'make regen-keyword'.
More trivial comment -> docstring transformations by Ka-Ping Yee, who writes: Here is batch 2, as a big collection of CVS context diffs. Along with moving comments into docstrings, i've added a couple of missing docstrings and attempted to make sure more module docstrings begin with a one-line summary. I did not add docstrings to the methods in profile.py for fear of upsetting any careful optimizations there, though i did move class documentation into class docstrings. The convention i'm using is to leave credits/version/copyright type of stuff in # comments, and move the rest of the descriptive stuff about module usage into module docstrings. Hope this is okay.
2000-02-04 11:10:34 -04:00
"""
Ka-Ping Yee's version is better: Here's a "keyword" module which, in the spirit of "token.py", updates the list of keywords automatically from a source file (in this case, "graminit.c" seemed like a reasonable choice, easier than "Grammar/Grammar"). You get "kwlist", a sorted list of keywords; "kwdict", a dictionary mapping each keyword to 1; and "iskeyword", a function which tells you if a given string happens to be a keyword.
1997-03-20 15:45:51 -04:00
Include soft keywords in keyword.py (GH-20877)
2020-06-14 23:55:15 -03:00
__all__ = ["iskeyword", "issoftkeyword", "kwlist", "softkwlist"]
a few more modules get __all__
2001-01-24 02:27:27 -04:00
Ka-Ping Yee's version is better: Here's a "keyword" module which, in the spirit of "token.py", updates the list of keywords automatically from a source file (in this case, "graminit.c" seemed like a reasonable choice, easier than "Grammar/Grammar"). You get "kwlist", a sorted list of keywords; "kwdict", a dictionary mapping each keyword to 1; and "iskeyword", a function which tells you if a given string happens to be a keyword.
1997-03-20 15:45:51 -04:00
kwlist = [
bpo-36143: Regenerate Lib/keyword.py from the Grammar and Tokens file using pgen (GH-12456) Now that the parser generator is written in Python (Parser/pgen) we can make use of it to regenerate the Lib/keyword file that contains the language keywords instead of parsing the autogenerated grammar files. This also allows checking in the CI that the autogenerated files are up to date.
2019-03-25 19:01:12 -03:00
'False',
'None',
'True',
'and',
'as',
'assert',
'async',
'await',
'break',
'class',
'continue',
'def',
'del',
'elif',
'else',
'except',
'finally',
'for',
'from',
'global',
'if',
'import',
'in',
'is',
'lambda',
'nonlocal',
'not',
'or',
'pass',
'raise',
'return',
'try',
'while',
'with',
'yield'
]
bpo-35975: Support parsing earlier minor versions of Python 3 (GH-12086) This adds a `feature_version` flag to `ast.parse()` (documented) and `compile()` (hidden) that allow tweaking the parser to support older versions of the grammar. In particular if `feature_version` is 5 or 6, the hacks for the `async` and `await` keyword from PEP 492 are reinstated. (For 7 or higher, these are unconditionally treated as keywords, but they are still special tokens rather than `NAME` tokens that the parser driver recognizes.) https://bugs.python.org/issue35975
2019-03-07 16:38:08 -04:00
Include soft keywords in keyword.py (GH-20877)
2020-06-14 23:55:15 -03:00
softkwlist = [
bpo-42128: Structural Pattern Matching (PEP 634) (GH-22917) Co-authored-by: Guido van Rossum <guido@python.org> Co-authored-by: Talin <viridia@gmail.com> Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
2021-02-26 18:51:55 -04:00
'_',
'case',
gh-103763: Implement PEP 695 (#103764) This implements PEP 695, Type Parameter Syntax. It adds support for: - Generic functions (def func[T](): ...) - Generic classes (class X[T](): ...) - Type aliases (type X = ...) - New scoping when the new syntax is used within a class body - Compiler and interpreter changes to support the new syntax and scoping rules Co-authored-by: Marc Mueller <30130371+cdce8p@users.noreply.github.com> Co-authored-by: Eric Traut <eric@traut.com> Co-authored-by: Larry Hastings <larry@hastings.org> Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
2023-05-16 00:36:23 -03:00
'match',
'type'
Include soft keywords in keyword.py (GH-20877)
2020-06-14 23:55:15 -03:00
]
SF patch #852140: keyword.py - use __contains__ and bool Use a set instead of dict with values equal to one.
2003-12-02 03:48:15 -04:00
iskeyword = frozenset(kwlist).__contains__
Include soft keywords in keyword.py (GH-20877)
2020-06-14 23:55:15 -03:00
issoftkeyword = frozenset(softkwlist).__contains__