[issue37353] Source code has not always been forward-compatible

miss-islington added the comment: New changeset 0ab6b01820afef44beea8158ba08b6469bf264a0 by Miss Islington (bot) in branch '3.8': bpo-37353: Updated parser note about source code compatibility(GH-14277) https://github.com/python/cpython/commit/0ab6b01820afef44beea8158ba08b6469bf264a0

[issue37353] Source code has not always been forward-compatible

miss-islington added the comment: New changeset 2552e27b752f449b1d7046b384b14db0a69f46ad by Miss Islington (bot) in branch '3.7': bpo-37353: Updated parser note about source code compatibility(GH-14277) https://github.com/python/cpython/commit/2552e27b752f449b1d7046b384b14db0a69f46ad

[issue37353] Source code has not always been forward-compatible

Change by Zachary Ware : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___

[issue37353] Source code has not always been forward-compatible

Change by miss-islington : -- pull_requests: +15881 pull_request: https://github.com/python/cpython/pull/16295 ___ Python tracker ___

[issue37353] Source code has not always been forward-compatible

Change by miss-islington : -- pull_requests: +15880 pull_request: https://github.com/python/cpython/pull/16294 ___ Python tracker ___

[issue37353] Source code has not always been forward-compatible

Zachary Ware added the comment: New changeset 062cfe3b11c61d03ccc2915e360f9b0d80e23642 by Zachary Ware (Prateek Nayak) in branch 'master': bpo-37353: Updated parser note about source code compatibility(GH-14277)

[issue37353] Source code has not always been forward-compatible

Change by Prateek Nayak : -- keywords: +patch pull_requests: +14101 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14277 ___ Python tracker ___

[issue37353] Source code has not always been forward-compatible

Carol Willing added the comment: "...though source code has usually been forward-compatible within a major release series." Agree with your thoughts Julien and Zach. Perhaps remove "whereas" as well. -- nosy: +willingc ___ Python tracker

[issue37353] Source code has not always been forward-compatible

Zachary Ware added the comment: Perhaps just adding "within a major release series" after "forward-compatible" would be sufficient? -- nosy: +zach.ware ___ Python tracker

[issue37353] Source code has not always been forward-compatible

New submission from Julien Palard : In Doc/library/parser.rst I can read: The parse trees are not typically compatible from one version to another, whereas source code has always been forward-compatible. But I don't think this is right, I think of print for example. Maybe just remove ",