Hopefully Pablo's proposed solution works. If it doesn't, could this one optimization be left in the peephole optimizer at bytecode level? Otherwise is another solution to follow through with https://discuss.python.org/t/switch-pythons-parsing-tech-to-something-more-powerful-than-ll-1/379 and switch the parser so it can handle all syntax errors on its own without support from the AST analyzer? _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/LN236JC6M3IGPC6GT43TCEOJRDNLO53T/
- [Python-Dev] Re: Removing dead bytecode vs repo... Pablo Galindo Salgado
- [Python-Dev] Re: Removing dead bytecode vs ... Ned Batchelder
- [Python-Dev] Re: Removing dead bytecode vs repo... Neil Schemenauer
- [Python-Dev] Re: Removing dead bytecode vs reporting... Tim Peters
- [Python-Dev] Re: Removing dead bytecode vs repo... Pablo Galindo Salgado
- [Python-Dev] Re: Removing dead bytecode vs reporting... Pablo Galindo Salgado
- [Python-Dev] Re: Removing dead bytecode vs reporting... Terry Reedy
- [Python-Dev] Re: Removing dead bytecode vs repo... Pablo Galindo Salgado
- [Python-Dev] Re: Removing dead bytecode vs reporting... Pablo Galindo Salgado
- [Python-Dev] Re: Removing dead bytecode vs repo... Brett Cannon
- [Python-Dev] Re: Removing dead bytecode vs ... Guido van Rossum
- [Python-Dev] Re: Removing dead bytecode vs ... Pablo Galindo Salgado