[issue25733] Idle does not handle non-standard compile errors

ppperry added the comment: Why does compile not support null bytes in the first place? -- ___ Python tracker ___ ___ Python-bugs-list

[issue25733] Idle does not handle non-standard compile errors

Terry J. Reedy added the comment: How lovely ;-) >>> compile(chr(0), '', 'eval') # 2.7, chr(0) is byte Traceback (most recent call last): File "", line 1, in compile(chr(0), '', 'eval') TypeError: compile() expected string without null bytes >>> compile(chr(0), '', 'eval') # 3.4, chr

[issue25733] Idle does not handle non-standard compile errors

ppperry added the comment: A similar problem occurs with the TypeError produced by attempting to compile a null byte. -- ___ Python tracker ___ _

[issue25733] Idle does not handle non-standard compile errors

Terry J. Reedy added the comment: I believe startup files are compiled in PyShell.py, line 649 (3.x) try: code = compile(source, filename, "exec") except (OverflowError, SyntaxError): and editor code is compiled in ScriptBinding.py, line 100 try: #

[issue25733] Idle does not handle non-standard compile errors

Changes by Terry J. Reedy : -- assignee: -> terry.reedy stage: -> needs patch versions: +Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___ _

[issue25733] Idle does not handle non-standard compile errors

Changes by ppperry : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue25733] Idle does not handle non-standard compile errors

New submission from ppperry: The following code: for a in range(26): for b in range(26): for c in range(26): for d in range(26): for e in range(26): for f in range(26): for g in range(26): for h in range(26): for i in range(26): for j in range