-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Improve the IDLE - console differences doc #79280
Comments
Differences added in initial PR:
Dependencies bpo-33000 is about finite versus infinite buffer. Or should any of these be in new Shell subsection? |
Just a comment on usage, for what it's worth: I don't know how common the term "console" is on modern Windows systems, but I think the term has a very different meaning on Unix and macOS. In those environments, if used at all, a "console" *might* refer to a window that provides access to admin functions. A normal (non-admin) user would not use or even be familiar with the term "console" in this context. A more familiar term would be a "terminal window" or "shell window" or some such. But I'm not sure I even understand totally what is meant by "console" here; it's just sounds foreign :) |
By 'console' I mean the text-interface window that Python normally runs in, whether in batch or interactive mode, whether started directly from an icon or menu or file listing or indirectly by entering 'python' in a shell program running in the console. (On Windows, there is only the one text UI program.) On Windows, 'console' is the proper term (as Eryk Sun has taken pains to point out). "Command Prompt' (cmd.exe)*, 'PowerShell' (???.exe) and Python (python.exe, when run directly without using either command-line program) all use the same console as their UI. In all cases, the app interacts with users through a console window just as IDLE interacts with users through tk windows. *Naive Windows users sometimes call a console window a Command Prompt window or every a Dos Prompt window, even when Python is running in such a window without cmd.exe. In all cases, clicking the icon in the upper left corner displays the console menu. Selecting 'Properties' displays the console properties dialog. Selecting the 'Options' tab displays an option to use the 'legacy console' rather than the 'new console'. I appreciate being informed that the naked term does not work for other systems. Would it be sufficient to define 'console' as the text interface window that Python normally runs in, which might instead be caller a terminal, terminal window, or shell window? I would rather not have to use 'console or terminal' everywhere. 'IDLE - console differences' is about differences in execution result and output display* when running Python code through IDLE (using tk) instead of Python in its standard running-in-a-console mode. Do you have a better idea of how to reduce this to a few words? How about 'IDLE - console Python differences', with an explanation of 'console Python'? ('terminal Python' reminds me of dead parrots ;-) (Since I opened this issue, I realized that the pasting difference is a code preparation difference that belongs elsewhere.) |
Thanks for the explanation. That's what I thought you meant but it's good to make sure. I'm not sure what the best solution is and others might have a different opinion. It might be good to solicit some feedback from a wider audience of users who do not have Windows experience. |
I thought of 'IDLE versus standard Python', or 'default Python', but the contrast is not correct, as IDLE uses the same Python. The intended contrast is between the result of different methods of running Python code with a particular Python binary. 'How IDLE modifies execution results' is correct, but I don't especially like it. I can ask for other opinions on idledev and python-list. In the meanwhile, I have a patch nearly ready, and want to move on to the dependency issues that will edit the same section. So while waiting for opinions, I want to merge a version of what I have, but leave this open pending a final decision on the title and terminology. |
I either removed or augmented occurrences of 'console' in the renamed section. |
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: