A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084340.html below:

[Python-Dev] Reindenting the C code base?

[Python-Dev] Reindenting the C code base?Alexandre Vassalotti alexandre at peadrop.com
Sun Dec 14 18:54:15 CET 2008
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).

-- Alexandre
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4