Terry J. Reedy <tjre...@udel.edu> added the comment:
'Not working' reports lacking information needed to respond, whether to help the reporter of fix a bug, are a common beginner mistake. The problem is especially acute for IDLE since it is especially targeted at beginners, who may not know the difference between generic python problems and specific IDLE (or tkinter) problems (or even user code bugs). And beginners may not understand 'try running python (or IDLE) in a command line (or terminal or console)'. And beginning programmers who have never shared software with other may have no idea what (relatively) large volume of information the authors may to proceed. So I am making this issue about adding information to the IDLE doc about things a user should try and information to include when reporting. ---------- stage: -> needs patch status: pending -> open title: IDLE not working -> IDLE: Document info needed for 'not working' reports. versions: +Python 3.10 -Python 3.8 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40685> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
