[issue7676] IDLE shell shouldn't use TABs

Change by Stephen Paul Chappell : -- nosy: -Zero ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: I think that using tabs for Shell indents is IDLE's current worst design wart. But I agree with KBK (#1196946) that merely replacing tabs with spaces does not really solve the problem, which is the jagged physical margin consequent on physically indenting

[issue7676] IDLE shell shouldn't use TABs

Louie Lu added the comment: In #30663, I add the line number sidebar to editor window. I've attempted to do the same in pyshell, something different that need to concern is the indent prompt showing. -- nosy: +louielu ___ Python tracker

[issue7676] IDLE shell shouldn't use TABs

Changes by irdb : -- nosy: +irdb ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: I believe I explained above the logical and technical factors that make the Idle shell inherently different from the console shell in this regard. As the title says, this issue is about not using tabs and not about mixing tabs and spaces. As I already said,

[issue7676] IDLE shell shouldn't use TABs

Al Sweigart added the comment: There are three pieces of user-specified configuration: (1) the number of spaces for a tab set in IDLE's config, (2) the sys.ps1 value, and (3) the sys.ps2 value. Currently IDLE's shell is ignoring (1) while the editor is not. IDLE's shell is ignoring (3) while

[issue7676] IDLE shell shouldn't use TABs

Changes by Al Sweigart asweig...@gmail.com: -- nosy: +Al.Sweigart ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7676 ___ ___ Python-bugs-list

[issue7676] IDLE shell shouldn't use TABs

Stephen Paul Chappell added the comment: In Lib\idlelib\PyShell.py, there are usetabs and indentwidth attributes in the PyShell class. Is there some reason that these settings cannot be reconfigured in the Options Configure IDLE... menu? I just edited these to False and 4 respectively and am

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: They potentially could be. However, if the result is something like if a: if b: print(a+b) or worse, with Lucida Sans Unicode, the visual equivalent of if a: if b: print(a+b) then I do not find result very satisfactory. I think moving the

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: To continue and expand some things I said in various messages above... The reason Shell does not and indeed should not have a secondary line prompt is that in Shell, ' ' means 'Enter a statement:' rather than just a line. Being able to enter, edit, and recall

[issue7676] IDLE shell shouldn't use TABs

Stephen Paul Chappell added the comment: If you want the IDLE shell to be as consistent as possible with the editor windows, changing the TAB binding to insert four spaces instead of a tab (alternative 2) would be helpful. -- ___ Python tracker

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: The problem with just /\t// is the absence of a secondary prompt. def f(): return 'not acceptible' Hence the 8+4+4... proposal. With a proportional font, the return would start to the *left* of def. Adding '... ' works for fixed pitch fonts, but

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: Raymond, I cannot program 'fix it'. I need an exact spec. I suspect that any change will upset someone. Which of the four alternative proposals would you consider to be an improvement? One of the problems is that what might look good on screen with colors,

[issue7676] IDLE shell shouldn't use TABs

Raymond Hettinger added the comment: [Cherniavsky Beni] it's makes copy-paste code between the shell and editor windows confusing This has been a continual source of frustration for students in my Python courses as well. I'm looking forward to it being fixed. -- priority: normal -

[issue7676] IDLE shell shouldn't use TABs

Changes by Stephen Paul Chappell noctis.skyto...@gmail.com: -- nosy: +Zero versions: +Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7676 ___

[issue7676] IDLE shell shouldn't use TABs

Changes by Terry J. Reedy tjre...@udel.edu: -- versions: -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7676 ___ ___

[issue7676] IDLE shell shouldn't use TABs

Westley Martínez added the comment: I think the prompt should be in margins, completely separate from the input. It is just meant to be a guide anyway, and make this would make it easy to copy code from the interactive shell to a file. I think output should be in a separate window or frame

[issue7676] IDLE shell shouldn't use TABs

Raymond Hettinger added the comment: IDLE defaults to indenting with 4 spaces in editor windows, but hard TABs in the Python Shell window. This is inconsistent with PEP 8; what's worse, it's makes copy-paste code between the shell and editor windows confusing and dangerous! I also teach

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy added the comment: Continuing my last post ... Fix 4 is to put prompts in a narrow window to the left of and kept in synch with the main shell input/output window. This is the approach used by Heblikar in #17535. -- ___ Python

[issue7676] IDLE shell shouldn't use TABs

Kamushin Shen added the comment: I'm a GSOC student. And I submit this patch as a part of my proposal. This patch solve the copy-paste problem by judging the first line. However, it seems a little ugly in IDLE. -- nosy: +Kamushin.Shen Added file:

[issue7676] IDLE shell shouldn't use TABs

Terry J. Reedy tjre...@udel.edu added the comment: I closed #8285 as it merely reported a consequence of using tabs. The Command Prompt window used for interactive Python on Windows only uses fixed-pitch fonts. Idle (tk) allows any font. I happen to use Lucida Sans Unicode (variable pitch)

[issue7676] IDLE shell shouldn't use TABs

Roger Serwy roger.se...@gmail.com added the comment: Here's a simple patch to fix this bug. The prompt causes the first level of indented code to use 8 spaces. Further indented code should use 4 spaces, but still uses 8 spaces likely due to the bug described in #8285. -- keywords:

[issue7676] IDLE shell shouldn't use TABs

Cherniavsky Beni c...@users.sf.net added the comment: This is almost a duplicate of http://bugs.python.org/issue1196946 (though the solution there took a different direction). -- ___ Python tracker rep...@bugs.python.org

[issue7676] IDLE shell shouldn't use TABs

Changes by Tal Einat talei...@gmail.com: -- nosy: +taleinat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7676 ___ ___ Python-bugs-list mailing

[issue7676] IDLE shell shouldn't use TABs

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- assignee: - kbk nosy: +kbk stage: - needs patch versions: +Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7676

[issue7676] IDLE shell shouldn't use TABs

New submission from Cherniavsky Beni c...@users.sf.net: IDLE defaults to indenting with 4 spaces in editor windows, but hard TABs in the Python Shell window. This is inconsistent with PEP 8; what's worse, it's makes copy-paste code between the shell and editor windows confusing and