[issue36256] parser module fails on legal input

Pablo Galindo Salgado added the comment: 3.6 only accepts security fixes at this point. -- ___ Python tracker ___ ___ Python-bugs-l

[issue36256] parser module fails on legal input

A. Skrobov added the comment: Is it intentional that the fix is not backported to 3.6 as well? -- ___ Python tracker ___ ___ Python

[issue36256] parser module fails on legal input

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue36256] parser module fails on legal input

Pablo Galindo Salgado added the comment: New changeset 00eb97b4a7d9a73b88ed7c76faee4e49204d5a00 by Pablo Galindo (Miss Islington (bot)) in branch '3.7': bpo-36256: Fix bug in parsermodule when parsing if statements (GH-12488) https://github.com/python/cpython/commit/00eb97b4a7d9a73b88ed7c76fa

[issue36256] parser module fails on legal input

Change by miss-islington : -- pull_requests: +12440 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue36256] parser module fails on legal input

Pablo Galindo Salgado added the comment: New changeset 9ad15d27361eaa47b77600c7c00a9787a894 by Pablo Galindo in branch 'master': bpo-36256: Fix bug in parsermodule when parsing if statements (GH-12477) https://github.com/python/cpython/commit/9ad15d27361eaa47b77600c7c00a9787a894 ---

[issue36256] parser module fails on legal input

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +12429 stage: -> patch review ___ Python tracker ___ ___ Pytho

[issue36256] parser module fails on legal input

Brett Cannon added the comment: @Xavier different needs; AST and CST are at different stages of compilation. -- ___ Python tracker ___

[issue36256] parser module fails on legal input

Xavier Combelle added the comment: never used the parser module nor lib2to3. Does they have any advantage over ast.parse and ast module ? -- ___ Python tracker ___ __

[issue36256] parser module fails on legal input

Brett Cannon added the comment: It's sounding like it might be worth the effort then to make lib2to3's parser not be a "hidden" thing in lib2to3, break it out as a new parser module (I have no stance on name), and then deprecate the old parser module. I think this was discussed at the last l

[issue36256] parser module fails on legal input

Change by Giampaolo Rodola' : -- nosy: -giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue36256] parser module fails on legal input

A. Skrobov added the comment: > The major problem with the parser module is that is unsynchronized with the > actual parser The parser module is "sort of" synchronised with the actual parser, in that it uses the same _PyParser_Grammar; this doesn't mean they always behave the same, as this

[issue36256] parser module fails on legal input

Pablo Galindo Salgado added the comment: > I would be curious to hear what Pablo has to say with the new parser having > landed and if there's something we should be exposing from that code to > replace what's in 'parser' today? (Either w/o semantic change or a new API.) :) One small clarif

[issue36256] parser module fails on legal input

Brett Cannon added the comment: I would be curious to hear what Pablo has to say with the new parser having landed and if there's something we should be exposing from that code to replace what's in 'parser' today? (Either w/o semantic change or a new API.) -- ___

[issue36256] parser module fails on legal input

New submission from A. Skrobov : Under #26526, I had optimised the validation code in parser module to use the actual parser DFAs, but my code considers only the token types in the input, and doesn't distinguish between different NAMEs (e.g. different keywords). The result is this: Python 3.