Message374282
| Author |
gvanrossum |
| Recipients |
brandtbucher, gvanrossum, lys.nikolaou, miss-islington, ned.deily, nnemkin, pablogsal, vstinner |
| Date |
2020年07月25日.21:25:46 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1595712346.82.0.593141519773.issue40939@roundup.psfhosted.org> |
| In-reply-to |
| Content |
There are some difficulties with removing Grammar/Grammar, since it is used to generate the full grammar in the reference docs (Doc/reference/grammar.rst). Producing a similar grammar from the PEG grammar is currently painful because our PEG grammar contains a number of "invalid_*" rules that just exist to be able to produce more useful error messages.
See https://github.com/we-like-parsers/cpython/issues/135.
The continued existence of Grammar/Grammar has confused at least one person, see issue41362.
Grepping for Grammar/Grammar in the docs, there are a few other occurrences:
library/token.rst:14:of the parse tree (terminal tokens). Refer to the file :file:`Grammar/Grammar`
library/parser.rst:43::file:`Grammar/Grammar` in the standard Python distribution. The parse trees
library/symbol.rst:15:names. Refer to the file :file:`Grammar/Grammar` in the Python distribution for
reference/grammar.rst:7:.. literalinclude:: ../../Grammar/Grammar |
|