[Python-Dev] Reindenting the C code base?

Guido van Rossum guido at python.org
Sun Dec 14 17:26:06 CET 2008


On Sat, Dec 13, 2008 at 2:11 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Guido van Rossum <guido <at> python.org> writes:
>>
>> I think we should not do this. We should use 4 space indents for new
>> files, but existing files should not be reindented.
>
> Well, right now many files are indented with a mix of spaces and tabs, depending
> on who did the edit and how their editor was configured at the time.

That's  a shame. We used to have more rigorous standards than allowing that.

> Perhaps a graceful policy would be to mandate that all new edits be made with
> spaces without touching other functions in the file. Then hopefully the code
> base would gradually converge to a tabless scheme.

I don't think so. I find local consistency more important than global
consistency. A file can become really hard to read when different
indentation schemes are used in random parts of the code.

If you have a problem configuring your editor, just say so and someone
will explain how to do it.

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


More information about the Python-Dev mailing list