[Python-Dev] Reindenting the C code base?

Guido van Rossum guido at python.org
Mon Dec 15 21:59:30 CET 2008

Aha! A specific file. I'm supportive of fixing that specific file. Now
if you can figure out how to do it and still allow merging between 2.6
and 3.0 that would be cool.

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

On Sun, Dec 14, 2008 at 9:54 AM, Alexandre Vassalotti
<alexandre at peadrop.com> wrote:
> On Sat, Dec 13, 2008 at 5: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.
> Personally, I think the indentation of, at least,
> Objects/unicodeobject.c should be fixed. This file has become so
> mixed-up with tab and space indents that I have no-idea what to use
> when I edit it. Just to give an idea how messy it is, they are 5214
> lines indented with tabs and 4272 indented with spaces (out the 9733
> of the file).

More information about the Python-Dev mailing list