Author terry.reedy
Recipients Coder436, eric.smith, terry.reedy
Date 2020-05-22.04:23:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590121429.54.0.902977127979.issue40685@roundup.psfhosted.org>
In-reply-to
Content
'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.
History
Date User Action Args
2020-05-22 04:23:49terry.reedysetrecipients: + terry.reedy, eric.smith, Coder436
2020-05-22 04:23:49terry.reedysetmessageid: <1590121429.54.0.902977127979.issue40685@roundup.psfhosted.org>
2020-05-22 04:23:49terry.reedylinkissue40685 messages
2020-05-22 04:23:49terry.reedycreate