-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
IDLE: change Shell window title #85941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The IDLE Shell window title is set with pyshell line 836 In bpo-41765, Mark Summerfield suggested in a side-comment that the title should be 'IDLE'. E. Paine agreed that it should be changed, suggesting that it contributes to the fact that "there are lots people when first starting who think the IDLE shell *is the* Python shell". I have noticed this fact on Stackoverflow, where about half the questions tagged 'python-idle' have nothing to do with IDLE. (I regularly remove such mistaken tags.) I have wondered why and how to better counter this. For one thing, it results in users blaming IDLE for Python behavior, such as not running buggy code. I never noticed before that IDLE promotes the confusion a bit in the shell title. Issues such as bpo-37903 (move prompt to shell sidebar, which I am planning to review soon) and bpo-37892 (separate input area) will differentiate the IDLE Shell from the standard REPL even more. Paine suggested 'IDLE <version> Shell'. I don't want to suggest that IDLE is independently versioned, and prefer 'IDLE Shell (<version>)'. The parenthesized version is used for editor windows (and was also added by bpo-17390). On Windows, mousing over a taskbar icon initially shows about 10-14 variable-width letters of the title. Is 'Shell' or '3.x.y' more important to be ensured of visibility? Other suggestions and comments? [If IDLE becomes a tabbed-window application, the window title would be 'IDLE (version)' and the shell would be on a 'Shell' tab.] |
In the last few months, there has been an increase in bpo issues mis-tagged IDLE. Today's example: bpo-41774 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: