bpo-37353: Updated parser note about source code compatibility(GH-14277)
(cherry picked from commit 062cfe3b11
)
Co-authored-by: Prateek Nayak <45075669+Kriyszig@users.noreply.github.com>
This commit is contained in:
parent
fb7746d5d1
commit
0ab6b01820
|
@ -51,7 +51,8 @@ Python version to another as source text will always allow correct parse trees
|
|||
to be created in the target version, with the only restriction being that
|
||||
migrating to an older version of the interpreter will not support more recent
|
||||
language constructs. The parse trees are not typically compatible from one
|
||||
version to another, whereas source code has always been forward-compatible.
|
||||
version to another, though source code has usually been forward-compatible within
|
||||
a major release series.
|
||||
|
||||
Each element of the sequences returned by :func:`st2list` or :func:`st2tuple`
|
||||
has a simple form. Sequences representing non-terminal elements in the grammar
|
||||
|
|
Loading…
Reference in New Issue