You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using Idle to teach beginning programming to university
students for the last 6 or 7 years. I've taught hundreds and hundreds of
students, and the single biggest confusion with Idle is this:
"New Window" in the file menu is ambiguous
Proposed fix: change "New Window" to "New File", or "New Program"
Many beginners don't get the difference between a shell window and
program window. I spend some time explaining the difference, and yet
they see "New Window" and don't know if this means a shell window or
program window.
Obviously this is not an issue for non-beginners, or even for anyone
willing to experiment for a minute or two, but it seems to me this is a
small change that could be useful to beginners.
Plus more precise menu options are usually a good thing in general.
This issue is mentioned as part of bpo-13504 meta-issue.
The attached patch extends Tal's original patch by also updating the help.txt documentation.
RamchandraApte commented on Dec 8, 2011
RamchandraAptemannequin
Mannequin
More actions
+1 on renaming New Window to New File
rovitotv commented on May 30, 2013
rovitotvmannequin
Mannequin
More actions
Roger's patch works but the documentation has changed since he made the patch back in 2011. So I patched the patch and hope this very simple patch will get committed. I will work on a patch for 2.7 next.
Today I was teaching a student on how to use Python with IDLE and the student found the existing menu option confusing. I was thrilled a patch already existed and it just needed updated. Thanks!
rovitotv commented on May 30, 2013
rovitotvmannequin
Mannequin
More actions
Same patch but for Python 2.7.5. I just updated the documentation from Roger's excellent patch.
For some reason, the idlelib/help.txt was reformatted with double indents (not sure I like this) for 3.4 but not 3.3. So parts of the patch against 3.4 would not apply to 3.3, which must be patched first. And the merge to 3.4 likewise failed for two files. We should have the same text for all versions except where is actually matters. Or replace with the doc, as proposed elsewhere.
The 'new window' issue is "Blank file editor window for a new file" versus "File editor window pre-loaded with existing file". "New file" captures the difference between the two where as "New window" is the same for both. So even native English speaker could be initially confused. When I tested, "New file" looks right. File / New may be standard on Windows, but File / New File looks fine to me.
Toby, thank you for sharing your experience. We need more of such, even if we have been slow to respond.
Terry I am sorry the push didn't go smooth. I thought I had checked the patch with 2.7 and 3.4 and it applied for me but maybe I missed something? For sure I didn't check 3.3 but from here on out I will. Awhile ago I worked on a issue to synchronize the documentation here: http://bugs.python.org/issue5066
Mr. Andrew Svetlov was kind enough to push the patch but he only pushed it for 3.4 which I am not sure why? Then Zachary Ware had the excellent suggestion of making the help.txt generate from the rst file http://bugs.python.org/issue16893. So with all that being said I am confused about the direction of IDLE documentation. Maybe we should reopen bpo-5066 or create a new issue to sync help.txt and idle.rst across all version from 2.7 - 3.4? Then apply Zachary's patch to automate the creation of help.txt.
Activity
tjd commentedon Oct 15, 2009
I've been using Idle to teach beginning programming to university
students for the last 6 or 7 years. I've taught hundreds and hundreds of
students, and the single biggest confusion with Idle is this:
"New Window" in the file menu is ambiguous
Proposed fix: change "New Window" to "New File", or "New Program"
Many beginners don't get the difference between a shell window and
program window. I spend some time explaining the difference, and yet
they see "New Window" and don't know if this means a shell window or
program window.
Obviously this is not an issue for non-beginners, or even for anyone
willing to experiment for a minute or two, but it seems to me this is a
small change that could be useful to beginners.
Plus more precise menu options are usually a good thing in general.
taleinat commentedon Jul 20, 2010
+1 on renaming it "New File".
Patch attached for py3k.
serwy commentedon Dec 8, 2011
This issue is mentioned as part of bpo-13504 meta-issue.
The attached patch extends Tal's original patch by also updating the help.txt documentation.
RamchandraApte commentedon Dec 8, 2011
+1 on renaming New Window to New File
rovitotv commentedon May 30, 2013
Roger's patch works but the documentation has changed since he made the patch back in 2011. So I patched the patch and hope this very simple patch will get committed. I will work on a patch for 2.7 next.
Today I was teaching a student on how to use Python with IDLE and the student found the existing menu option confusing. I was thrilled a patch already existed and it just needed updated. Thanks!
rovitotv commentedon May 30, 2013
Same patch but for Python 2.7.5. I just updated the documentation from Roger's excellent patch.
serwy commentedon May 30, 2013
LGTM. Thanks Todd!
rovitotv commentedon Jul 1, 2013
PING!!!!
It has been a month since Roger's last comment on the patch looking good, can somebody please commit or post feedback. Thanks.
terryjreedy commentedon Jul 1, 2013
I am planning to commit. PS. Shorter names that include '27', '33', etc, are easier to work with ;-).
python-dev commentedon Jul 1, 2013
New changeset 26ef5d5d5c3e by Terry Jan Reedy in branch '2.7':
Issue bpo-7136: In the Idle File menu, "New Window" is renamed "New File".
http://hg.python.org/cpython/rev/26ef5d5d5c3e
New changeset c39ddff53694 by Terry Jan Reedy in branch '3.3':
Issue bpo-7136: In the Idle File menu, "New Window" is renamed "New File".
http://hg.python.org/cpython/rev/c39ddff53694
New changeset 5bc3d8d22a93 by Terry Jan Reedy in branch 'default':
(merge) Issue bpo-7136: In the Idle File menu, "New Window" is renamed "New File".
http://hg.python.org/cpython/rev/5bc3d8d22a93
terryjreedy commentedon Jul 1, 2013
For some reason, the idlelib/help.txt was reformatted with double indents (not sure I like this) for 3.4 but not 3.3. So parts of the patch against 3.4 would not apply to 3.3, which must be patched first. And the merge to 3.4 likewise failed for two files. We should have the same text for all versions except where is actually matters. Or replace with the doc, as proposed elsewhere.
The 'new window' issue is "Blank file editor window for a new file" versus "File editor window pre-loaded with existing file". "New file" captures the difference between the two where as "New window" is the same for both. So even native English speaker could be initially confused. When I tested, "New file" looks right. File / New may be standard on Windows, but File / New File looks fine to me.
Toby, thank you for sharing your experience. We need more of such, even if we have been slow to respond.
rovitotv commentedon Jul 1, 2013
Terry I am sorry the push didn't go smooth. I thought I had checked the patch with 2.7 and 3.4 and it applied for me but maybe I missed something? For sure I didn't check 3.3 but from here on out I will. Awhile ago I worked on a issue to synchronize the documentation here:
http://bugs.python.org/issue5066
Mr. Andrew Svetlov was kind enough to push the patch but he only pushed it for 3.4 which I am not sure why? Then Zachary Ware had the excellent suggestion of making the help.txt generate from the rst file http://bugs.python.org/issue16893. So with all that being said I am confused about the direction of IDLE documentation. Maybe we should reopen bpo-5066 or create a new issue to sync help.txt and idle.rst across all version from 2.7 - 3.4? Then apply Zachary's patch to automate the creation of help.txt.