[issue400760] _src.c: indentation, ParseTuple method names

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue451841] python-mode indentation bug

Change by admin : -- github: None -> 34985 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400763] posixmodule.c: ANSI-fying, indentation

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400761] _sre.c: indentation, ParseTuple method names

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400762] mmapmodule.c: ANSI-fying, indentation, names

Change by admin : ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400762] mmapmodule.c: ANSI-fying, indentation, names

Change by admin : -- github: None -> 32532 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400761] _sre.c: indentation, ParseTuple method names

Change by admin : -- github: None -> 32531 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400763] posixmodule.c: ANSI-fying, indentation

Change by admin : -- github: None -> 32533 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue400760] _src.c: indentation, ParseTuple method names

Change by admin : -- github: None -> 32530 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46792] Indentation not preserved with ruamel.yaml.round_trip_dump

Change by Eric V. Smith : -- title: Indentation now preserved with ruamel.yaml.round_trip_dump -> Indentation not preserved with ruamel.yaml.round_trip_dump ___ Python tracker <https://bugs.python.org/issu

[issue46792] Indentation now preserved with ruamel.yaml.round_trip_dump

Change by Zachary Ware : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46792] Indentation now preserved with ruamel.yaml.round_trip_dump

Eric V. Smith added the comment: This looks like an issue with ruamel.yaml, which is a third party package. You should report it to them. Good luck! -- nosy: +eric.smith ___ Python tracker

[issue46792] Indentation now preserved with ruamel.yaml.round_trip_dump

New submission from Harshini : I observed that the indentation is not preserved when I load and dump a YAML file using round_trip_dump from ruamel.yaml. For example, I have an input file with the data: Inventory: - name: Apples count: 10 vendors: - - vendor_name: xyz

[issue35957] Indentation explanation is unclear

Quang Lê Duy added the comment: Reading from the source code (Parser/tokenizer.c from line 1364 as in Python 3.10), I derive these as the actual indentation rules: – Tab makes the indentation amount the next multiple of 8. – Among lines with the same indentation amount in the same parent line

[issue43859] Improve syntax error for indentation errors

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43859] Improve syntax error for indentation errors

Pablo Galindo Salgado added the comment: New changeset 56c95dfe271b1242bdc8163d4677e311552c00cb by Pablo Galindo in branch 'master': bpo-43859: Improve the error message for IndentationError exceptions (GH-25431)

[issue43859] Improve syntax error for indentation errors

Change by Andre Roberge : -- nosy: +aroberge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43859] Improve syntax error for indentation errors

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +24162 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25431 ___ Python tracker

[issue43859] Improve syntax error for indentation errors

New submission from Pablo Galindo Salgado : The current indentation error is quite simplistic and it does not include the context of the statement that was associated with the indented block and where it was: >>> def foo(): ... if lel: ... x = 2 File ""

[issue42496] Don't change indentation of RST markup

Andrés Delfino added the comment: When I open a PR fixing mark-up it's because it has visual effects. -- ___ Python tracker ___ ___

[issue42496] Don't change indentation of RST markup

Georg Brandl added the comment: To be clear, this has nothing to do with the amount of indentation, but that the directive below (the versionadded) has 4 spaces, and the paragraph above had 5 before the change. Therefore the further-indented paragraph is taken as a blockquote

[issue42496] Don't change indentation of RST markup

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42496] Don't change indentation of RST markup

Raymond Hettinger added the comment: Thanks for checking. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue42496] Don't change indentation of RST markup

stack. New in version 3.6. LIST_TO_TUPLE Pops a list from the stack and pushes a tuple containing the same values. New in version 3.9. LIST_EXTEND(i) Calls list.extend(TOS1[-i], TOS). Used to build lists. New in version 3.9. """ One extra space added large

[issue42496] Don't change indentation of RST markup

Raymond Hettinger added the comment: If this does have a visual effect for readers or if it breaks strict Sphinx requirement, let me know. -- ___ Python tracker ___

[issue42496] Don't change indentation of RST markup

(I can cut and paste fragments from live, tested code). -- assignee: docs@python components: Documentation messages: 382030 nosy: adelfino, docs@python, gregory.p.smith, rhettinger priority: normal severity: normal status: open title: Don't change indentation of RST markup v

[issue35885] configparser: indentation

Łukasz Langa added the comment: Thanks for your contribution Ido Michael but I'm also -1 on the feature. .ini is an underspecified format and it's supposed to be interoperable between applications. Indenting keys sounds like a compatibility challenge. -- resolution: -> wont fix

[issue35885] configparser: indentation

Tal Einat added the comment: I'm -1 on making this change. Frankly, I think there are many better modern alternatives to ConfigParser, and I think we should avoid complicating it any further. -- nosy: +taleinat ___ Python tracker

[issue35885] configparser: indentation

Ido Michael added the comment: ping -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35885] configparser: indentation

Ido Michael added the comment: @SilentGhost Added documentation to the module and a test for a give space indent in the module test. -- ___ Python tracker ___

[issue35885] configparser: indentation

SilentGhost added the comment: Your PRs are missing documentation and tests. -- ___ Python tracker ___ ___ Python-bugs-list

[issue35885] configparser: indentation

Ido Michael added the comment: New PR: GH-18623 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35885] configparser: indentation

Change by Ido Michael : -- pull_requests: +17988 pull_request: https://github.com/python/cpython/pull/18623 ___ Python tracker ___

[issue35885] configparser: indentation

Change by Ido Michael : -- pull_requests: +17986 pull_request: https://github.com/python/cpython/pull/18621 ___ Python tracker ___

[issue35885] configparser: indentation

Change by Ido Michael : -- pull_requests: +17985 pull_request: https://github.com/python/cpython/pull/18620 ___ Python tracker ___

[issue35885] configparser: indentation

Ido Michael added the comment: Created PR GH-18522 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35885] configparser: indentation

Change by Ido Michael : -- keywords: +patch pull_requests: +17899 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18522 ___ Python tracker ___

[issue35885] configparser: indentation

SilentGhost added the comment: I would suggest adding indent parameter to the write method, it would default to an empty string and could be used directly in the formatting operation. -- nosy: +SilentGhost ___ Python tracker

[issue35885] configparser: indentation

Ido Michael added the comment: Can I take this? What needs to be done? adding an indent flag and if it's passed indent the keys? -- nosy: +Ido Michael ___ Python tracker ___

[issue39284] Flexible indentation

Eric V. Smith added the comment: Please discuss this idea on the python-ideas mailing list first. It would also certainly require a PEP. But I don't want to get your hopes up: there's almost no chance that this would be accepted. I'm going to close this issue. If the idea gains any

[issue39284] Flexible indentation

New submission from aggu : Indentation should not be "too strict", any number of leading whitespaces greater that its "parent" or "peer" should be allowed. For example, the following code should be allow: a = 1 # step 1 # step 1.1

[issue38496] Python3 allows mixture of tabs and spaces for indentation

Eric V. Smith added the comment: Thanks, Serhiy. This has been reported in 24260, so I'm closing this issue. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> TabError behavior doesn't match documentation type: -> behavior

[issue38496] Python3 allows mixture of tabs and spaces for indentation

Karthikeyan Singaravelan added the comment: Seems related issue24260 -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list

[issue38496] Python3 allows mixture of tabs and spaces for indentation

Serhiy Storchaka added the comment: Thank you for your report Mikko. Yes, the heuristic used in Python 3 is unable to catch all inconsistencies in using tabs and spaces. Such bug was already reported early. There should be an open issue. -- nosy: +serhiy.storchaka

[issue38496] Python3 allows mixture of tabs and spaces for indentation

Steven D'Aprano added the comment: I believe that the interpreter only requires that each block is consistent, not that all blocks in a module are consistent. -- nosy: +steven.daprano ___ Python tracker

[issue38496] Python3 allows mixture of tabs and spaces for indentation

Eric V. Smith added the comment: I can verify this on 3.7.4. -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list

[issue38496] Python3 allows mixture of tabs and spaces for indentation

New submission from Mikko Rantalainen : Contrary to PEP-8 (https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces) claiming "Python 3 disallows mixing the use of tabs and spaces for indentation", in reality Python 3 allows mixing tabs and spaces without warnings or errors. F

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Stefan Behnel added the comment: I don't think this should be backported. Pretty-printing is not a production relevant feature, more of a "debugging, diffing and help users see what they get" kind of feature. It's good to have it fixed for the future, but we shouldn't bother users with it

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Change by miss-islington : -- pull_requests: +12522 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Serhiy Storchaka added the comment: Should we backport this change? I am not sure. -- ___ Python tracker ___ ___ Python-bugs-list

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Serhiy Storchaka added the comment: New changeset 384b81d923addd52125e94470b11d2574ca266a9 by Serhiy Storchaka (Vladimir Surjaninov) in branch 'master': bpo-36407: Fix writing indentations of CDATA section (xml.dom.minidom). (GH-12514)

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Stefan Behnel added the comment: Yes, this case is incorrect. Pretty printing should not change character content inside of a simple tag. The PR looks good to me. -- versions: +Python 3.8 ___ Python tracker

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Change by Vladimir Surjaninov : -- keywords: +patch pull_requests: +12465 stage: -> patch review ___ Python tracker ___ ___

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

Change by Karthikeyan Singaravelan : -- nosy: +eli.bendersky, scoder, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list

[issue36407] xml.dom.minidom wrong indentation writing for CDATA section

New submission from Vladimir Surjaninov : If we are writing xml with CDATA section and leaving non-empty indentation and new-line parameters, a parent node of the section will contain useless indentation, that will be parsed as a text. Example: >>>doc = minidom.Document(

[issue35885] configparser: indentation

Emmanuel Arias added the comment: > I already have some example code for it Do you have a patch? -- nosy: +eamanu ___ Python tracker ___

[issue35957] Indentation explanation is unclear

Carol Willing added the comment: Assigning this to @Mariatta, to be worked on the mentored sprint at PyCon US Cleveland. Verify behavior and update documentation. -- assignee: docs@python -> Mariatta nosy: +Mariatta, willingc ___ Python tracker

[issue35957] Indentation explanation is unclear

Jérôme LAURENS added the comment: To be more precise, consider code def f(x): \tx=0 # 7 spaces + one tab return x # 8 spaces In cpython, both indentation levels are 8 and no indentation error is reported (this is the case where both tab size and alt tab size are equal

[issue35957] Indentation explanation is unclear

New submission from Jérôme LAURENS : https://docs.python.org/3/reference/lexical_analysis.html#indentation reads Point 1: "Tabs are replaced (from left to right) by one to eight spaces such that the total number of characters up to and including the replacement is a multiple of

[issue35885] configparser: indentation

Change by SilentGhost : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35885] configparser: indentation

New submission from mrs.red : The configparser module does not have an option for indentation. I would like to indent the keys by tabs. Maybe we could implement an option for that? I already have some example code for it. -- components: Library (Lib) messages: 334729 nosy: mrs.red

[issue33960] IDLE REPL: Strange indentation

Change by Terry J. Reedy : -- versions: +Python 3.7, Python 3.8 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing

Re: Python indentation (3 spaces)

On 2018-10-25 12:59:18 +0200, Antoon Pardon wrote: > On 20-10-18 14:38, Peter J. Holzer wrote: > > On 2018-10-16 06:37:56 +1100, Chris Angelico wrote: > >> On Tue, Oct 16, 2018 at 6:34 AM Peter J. Holzer wrote: > >>> On 2018-10-15 14:12:54 +0200, Antoon Pardon wrote: > On 13-10-18 09:37,

Re: Python indentation (3 spaces)

On 20-10-18 14:38, Peter J. Holzer wrote: > On 2018-10-16 06:37:56 +1100, Chris Angelico wrote: >> On Tue, Oct 16, 2018 at 6:34 AM Peter J. Holzer wrote: >>> On 2018-10-15 14:12:54 +0200, Antoon Pardon wrote: On 13-10-18 09:37, Peter J. Holzer wrote: > On 2018-10-09 09:55:34 +0200,

Re: Python indentation (3 spaces)

ange "shows up" (i.e., is rejected by the pre-commit hook of your version control system) you can't change anything which makes using a version control system rather pointless. So you still need to distinguish between "intended changes" and "unintended changes". Simply rej

Re: Python indentation (3 spaces)

On 10/15/2018 12:37 PM, Chris Angelico wrote: On Tue, Oct 16, 2018 at 6:34 AM Peter J. Holzer wrote: On 2018-10-15 14:12:54 +0200, Antoon Pardon wrote: Spaces that replaced a tab by accident, are easy to catch too. They are all those lines that show up when you do a diff with the previous

Re: Python indentation (3 spaces)

On Tue, Oct 16, 2018 at 9:16 AM D'Arcy Cain wrote: > > On 10/15/18 5:54 PM, Gregory Ewing wrote: > > Cameron Simpson wrote: > >> I can't express how pleasing it is to see the traditional vi-vs-emacs > >> wars supplanted by emacs-vs-emacs :-) > > > > We're the People's Front of Emacs, not the

Re: Python indentation (3 spaces)

On 10/15/18 5:54 PM, Gregory Ewing wrote: > Cameron Simpson wrote: >> I can't express how pleasing it is to see the traditional vi-vs-emacs >> wars supplanted by emacs-vs-emacs :-) > > We're the People's Front of Emacs, not the Emacs People's Front! I thought we were the People's Emacs Front.

Re: Python indentation (3 spaces)

Cameron Simpson wrote: I can't express how pleasing it is to see the traditional vi-vs-emacs wars supplanted by emacs-vs-emacs :-) We're the People's Front of Emacs, not the Emacs People's Front! -- Greg -- https://mail.python.org/mailman/listinfo/python-list

Re: Python indentation (3 spaces)

On Tue, Oct 16, 2018 at 8:03 AM Cameron Simpson wrote: > > > [ Marko and Rhdri discussing emacs indentation modes ... ] > > I can't express how pleasing it is to see the traditional vi-vs-emacs > wars supplanted by emacs-vs-emacs :-) > Which editor should I use - vi in emacs

Re: Python indentation (3 spaces)

[ Marko and Rhdri discussing emacs indentation modes ... ] I can't express how pleasing it is to see the traditional vi-vs-emacs wars supplanted by emacs-vs-emacs :-) Cheers, Cameron Simpson -- https://mail.python.org/mailman/listinfo/python-list

Re: Python indentation (3 spaces)

On Tue, Oct 16, 2018 at 6:34 AM Peter J. Holzer wrote: > > On 2018-10-15 14:12:54 +0200, Antoon Pardon wrote: > > On 13-10-18 09:37, Peter J. Holzer wrote: > > > On 2018-10-09 09:55:34 +0200, Antoon Pardon wrote: > > >> On 08-10-18 19:43, Peter J. Holzer wrote: > > >>> In practice it doesn't work

Re: Python indentation (3 spaces)

On 2018-10-15 14:12:54 +0200, Antoon Pardon wrote: > On 13-10-18 09:37, Peter J. Holzer wrote: > > On 2018-10-09 09:55:34 +0200, Antoon Pardon wrote: > >> On 08-10-18 19:43, Peter J. Holzer wrote: > >>> In practice it doesn't work in my experience. There is always someone in > >>> a team who was

Re: Python indentation (3 spaces)

> > If you used two-space tab stops and I used (the normal :-) eight, > comfortable indentations for you would rapidly become uncomfortably large > indentations for me. I'd care about that. Buy a bigger monitor :-). On a more serious note, I think the number of indentation level

Re: Python indentation (3 spaces)

On 2018-10-15 09:49:12 +1100, Cameron Simpson wrote: > On 15Oct2018 00:33, Peter J. Holzer wrote: > > On 2018-10-15 09:06:11 +1100, Chris Angelico wrote: > > > On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > > > > Chris Angelico : > > > > > Ta

Re: Python indentation (3 spaces)

On 15/10/18 16:41, Marko Rauhamaa wrote: Rhodri James : On 15/10/18 12:28, Marko Rauhamaa wrote: Try running emacs -q abc.c and observe the indentation depth. """User Option: c-basic-offset This style variable holds the basic offset between indentation level

Re: Python indentation (3 spaces)

Rhodri James : > On 15/10/18 12:28, Marko Rauhamaa wrote: >> Try running >> >> emacs -q abc.c >> >> and observe the indentation depth. > > """User Option: c-basic-offset > > This style variable holds the basic offset betw

Re: Python indentation (3 spaces)

On 15/10/18 12:28, Marko Rauhamaa wrote: Rhodri James : On 15/10/18 05:45, Marko Rauhamaa wrote: The two-space indentation is the out-of-the-box default for emacs. Ahem. It's the default for certain C styles. It's not even the default for C-mode itself, which is 4. You must be running

Re: Python indentation (3 spaces)

ur screen >>>> or your choices. >>> Theoretically I would agree with you: Just use a single tab per >>> indentation level and let the user decide whether that's displayed as 2, >>> 3, 4, or 8 spaces or 57 pixels or whatever. >>> >>> In practic

Re: Python indentation (3 spaces)

Rhodri James : > On 15/10/18 05:45, Marko Rauhamaa wrote: >> The two-space indentation is the out-of-the-box default for emacs. > > Ahem. It's the default for certain C styles. It's not even the default > for C-mode itself, which is 4. You must be running a different version

Re: Python indentation (3 spaces)

On 15/10/18 05:45, Marko Rauhamaa wrote: Chris Angelico : I'm saying I have never seen is this: On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: However, it is trumped by an older convention whereby the indentation levels go as follows: 0: 1: SPC SPC 2: SPC SPC SPC SPC

Re: Python indentation (3 spaces)

On 14/10/18 09:06, Peter J. Holzer wrote: On 2018-10-14 00:45:49 +, Grant Edwards wrote: On 2018-10-13, Peter J. Holzer wrote: For "just use tabs" to work, all of those tools would have to magically recognize that they're looking at Python source and adjust the tab size accordingly.

Re: Python indentation (3 spaces)

Chris Angelico : > On Mon, Oct 15, 2018 at 3:51 PM Marko Rauhamaa wrote: > I don't understand your point here. It prints a letter, then some > spaces, then a tab, then another letter. On my terminal, that displays > the tab by advancing to the next tab position. If I highlight to > select, it's

Re: Python indentation (3 spaces)

On Mon, Oct 15, 2018 at 3:51 PM Marko Rauhamaa wrote: > The two-space indentation is the out-of-the-box default for emacs. > However, the tab collapsing principle is a universal default. If you go > against it, you will have to educate more tools than your editor. For > example,

Re: Python indentation (3 spaces)

Chris Angelico : > I'm saying I have never seen is this: > > On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: >> However, it is trumped by an older >> convention whereby the indentation levels go as follows: >> >>0: >>1: SPC SPC >>2:

Re: Python indentation (3 spaces)

that I'm saying I have never seen is this: On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > However, it is trumped by an older > convention whereby the indentation levels go as follows: > >0: >1: SPC SPC >2: SPC SPC SPC SPC >3: SPC SPC SPC SPC SPC SPC

Re: Python indentation (3 spaces)

ly. So when you say: I've literally NEVER come across this as a convention. Not a single file that I have ever worked with has used it. Where is this convention from? I feel that there _must_ be some misunderstanding here. Maybe you misinterpreted Marko's description of how 8-column

Re: Python indentation (3 spaces)

On Mon, Oct 15, 2018 at 9:56 AM Alan Bawden wrote: > In my experience this is a very common way to assume that tabs will be > interpreted. Virtually every source-code file I have encountered since the > mid 1970s (for any programming language or operating system) has assumed > either this

Re: Python indentation (3 spaces)

Chris Angelico writes: > On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > > Chris Angelico : ... > > That *could* be the situation. However, it is trumped by an older > > convention whereby the indentation levels go as follows: > > > >0: > >

Re: Python indentation (3 spaces)

On 15Oct2018 00:33, Peter J. Holzer wrote: On 2018-10-15 09:06:11 +1100, Chris Angelico wrote: On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > Chris Angelico : > > Tabs for indentation have semantic meaning. Top-level has zero tabs. > > One indentation level is represe

Re: Python indentation (3 spaces)

On 2018-10-15 09:06:11 +1100, Chris Angelico wrote: > On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > > Chris Angelico : > > > Tabs for indentation have semantic meaning. Top-level has zero tabs. > > > One indentation level is represented by one tab. Two indenta

Re: Python indentation (3 spaces)

On Mon, Oct 15, 2018 at 8:56 AM Marko Rauhamaa wrote: > > Chris Angelico : > > > Tabs for indentation have semantic meaning. Top-level has zero tabs. > > One indentation level is represented by one tab. Two indentation > > levels? Two tabs. It's about as perfect a

Re: Python indentation (3 spaces)

Chris Angelico : > Tabs for indentation have semantic meaning. Top-level has zero tabs. > One indentation level is represented by one tab. Two indentation > levels? Two tabs. It's about as perfect a representation as you could > hope for. If you like your indentation levels to be as

Re: Python indentation (3 spaces)

ent tab width > >>> per language, but a different tab width per user. > >> > >> You work in a different environment than I do. for me, tab width > >> varies from one project to another (sometimes even in the same > >> language). I don't get to

Re: Python indentation (3 spaces)

rk in a different environment than I do. for me, tab width >> varies from one project to another (sometimes even in the same >> language). I don't get to pick just one tab width. > > But if you use only tabs for indentation, the tab width setting simply > does not matt

Re: Python indentation (3 spaces)

s from one project to another (sometimes even in the same > language). I don't get to pick just one tab width. You probably don't because you use spaces, not tabs. If everybody used tabs, why would anyone care about your tab width? Unless they look over your shoulder while you are typing, they won't

Re: Python indentation (3 spaces)

th. But if you use only tabs for indentation, the tab width setting simply does not matter. I'm in favour of using only tabs. There is a disadvantage only if you try to align something which is NOT an indentation level, e.g. when there are big string constants or list constants etc.

Re: Python indentation (3 spaces)

On 2018-10-13, Peter J. Holzer wrote: > >> For "just use tabs" to work, all of those tools would have to >> magically recognize that they're looking at Python source and adjust >> the tab size accordingly. That isn't going to happen. > > Well, no. The idea of "just use tabs" isn't have a

Re: Python indentation (3 spaces)

I would agree with you: Just use a single tab per > > indentation level and let the user decide whether that's displayed as 2, > > 3, 4, or 8 spaces or 57 pixels or whatever. > > > > In practice it doesn't work in my experience. There is always someone in > > a te

  1   2   3   4   5   6   7   8   9   10   >