[issue42123] Run parser twice; enable invalid_* rules only on the second run

Lysandros Nikolaou added the comment: New changeset 24a7c298d47658295673dc04d1b6d59f2b200a7c by Lysandros Nikolaou in branch '3.9': [3.9] bpo-42123: Run the parser two times and only enable invalid rules on the second run (GH-22111) (GH-23011) https://github.com/python/cpython/commit/24a7c29

[issue42123] Run parser twice; enable invalid_* rules only on the second run

Change by Lysandros Nikolaou : -- pull_requests: +21927 pull_request: https://github.com/python/cpython/pull/23011 ___ Python tracker ___ __

[issue42123] Run parser twice; enable invalid_* rules only on the second run

Change by Lysandros Nikolaou : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue42123] Run parser twice; enable invalid_* rules only on the second run

Lysandros Nikolaou added the comment: New changeset bca701403253379409dece03053dbd739c0bd059 by Lysandros Nikolaou in branch 'master': bpo-42123: Run the parser two times and only enable invalid rules on the second run (GH-22111) https://github.com/python/cpython/commit/bca701403253379409dec

[issue42123] Run parser twice; enable invalid_* rules only on the second run

Lysandros Nikolaou added the comment: We do not have a big corpus of SyntaxErrors to test against, but some manual testing of running a file with a SyntaxError after a long complex line 1000 times shows no slowdown. We keep the token stream for the second run, so we don't need to run the to

[issue42123] Run parser twice; enable invalid_* rules only on the second run

Terry J. Reedy added the comment: Since I do a lot of interactive compiling, I appreciate faster feedback. How much will the slowdown be on errors? -- nosy: +terry.reedy title: Run the two times, only enable invalid_* rules on the second run -> Run parser twice; enable invalid_* rul