[Python-Dev] Reindenting the C code base?

Guido van Rossum guido at python.org
Sat Dec 13 22:26:50 CET 2008


On Sat, Dec 13, 2008 at 1:22 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> I remember there were some talks of reindenting the C code base (from tabs to
> 4-space indents) after py3k is released, but I can't find the discussion thread
> again. Was a decision ever taken about it?

I think we should not do this. We should use 4 space indents for new
files, but existing files should not be reindented. If you reindent,
much of the history of the file is essentially lost -- "svn blame"
will blame whoever reindented the code, and it's a pain to go back.
There's also the issue of merging between the 2.x and 3.x branches,
which we still do.

As far as a decision, I think the de facto decision is to keep the
status quo, and I'm all for sticking with that.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)


More information about the Python-Dev mailing list