[issue25733] Code and IDLE should catch all compile errors.

Change by Terry J. Reedy : -- versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ ___ Python-bugs-list

[issue25733] Code and IDLE should catch all compile errors.

ppperry added the comment: >SystemError is serious bug. Please open separate issue for this. Done. I created issue27514 -- ___ Python tracker ___

[issue25733] Code and IDLE should catch all compile errors.

Terry J. Reedy added the comment: Code patch, still needs tests. ppperry, thanks. I may create a temporary big file when large memory tests are allowed. -- keywords: +patch stage: needs patch -> test needed Added file: http://bugs.python.org/file43351/catch_all_syntax_errors.diff

[issue25733] Code and IDLE should catch all compile errors.

ppperry added the comment: OverflowError is raised when one attempts to compile a string of 2**31 or more characters. -- ___ Python tracker ___

[issue25733] Code and IDLE should catch all compile errors.

Serhiy Storchaka added the comment: SystemError is serious bug. Please open separate issue for this. > Why does compile not support null bytes in the first place? Due to implementation detail of CPython tokenizer. I uses NUL-terminated C strings. Yet one possible exception: MemoryError. I

[issue25733] Code and IDLE should catch all compile errors.

Terry J. Reedy added the comment: How to cause SyntaxError -- obvious NameError -- ?, already caught in code module OverflowError-- ?, already caught in code module SystemError - 22 nested for loops ('deeply nested blocks') TypeError -- chr(0), 2.7 ValueError -- chr(0), 3.x; bytes(0), 2.7