Terry J. Reedy added the comment:
There is still something you left out. Entering either print(")<return> or
print(')<return> at either a shell prompt or in a file and running the file
should result in "SyntaxError: EOL while scanning string literal", as Steven
said. Ditto for eval("print(')") or eval('print(")'). The error comes from
Python's compile() function. The result *should* be the same on all systems.
This is feature, neither a crash nor a bug. So my first inclination was to
close this as 'Not a bug'.
But getting a system crash log is usually a bug when running Python code. From
my reading of Mac's crash log, what crashed is not IDLE but Python running
_tkinter calling tcl running tk calling OSX's CoreFoundation which raised
NSRangeException. How did you bypass compile()?
Where did you get the Python that you installed? If from python.org, did you
pay attention to https://www.python.org/download/mac/tcltk/ and install a
tcl/tk that works? If not, not our bug.
Ned and Serhiy: can we patch _tkinter on Mac to refuse to run with the buggy
Apple tcl/tk? Or at least pop up a Warning box that says to not bug us when it
crashes?
----------
components: +Tkinter, macOS
nosy: +ned.deily, ronaldoussoren, serhiy.storchaka
type: -> crash
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue31142>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
