This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author John Smith
Recipients John Smith, gvanrossum, taleinat, terry.reedy
Date 2020-02-23.09:26:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582449975.3.0.466104865481.issue39724@roundup.psfhosted.org>
In-reply-to
Content
Interesting finding. Just some thoughs: I have to disagree on the "the experience with input() in IDLE is more useful and less confusing, especially to beginners" part.

Here are some reasons:

1. If a beginner starts with threading and expect a concurrent execution the confusion will be high if there is non in IDLE => implicitly changes of the runtime behavior siliencly enforced by an IDE can lead to misconcepts.

2. It took me (and my team) more than one hour to track a strange issue down to this IDLE related behavior - mainly because I assumed that IDLE would not change the runtime behavior of a program in that way => the deviation in behavior can even confuse experienced developers.

3. During my search I came across several reports of similar issues and most people were told to simply quit IDLE => "quirks" have impact on the reputation.

Personally I like and mainly use IDLE and would like to continue with it.
History
Date User Action Args
2020-02-23 09:26:15John Smithsetrecipients: + John Smith, gvanrossum, terry.reedy, taleinat
2020-02-23 09:26:15John Smithsetmessageid: <1582449975.3.0.466104865481.issue39724@roundup.psfhosted.org>
2020-02-23 09:26:15John Smithlinkissue39724 messages
2020-02-23 09:26:15John Smithcreate