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/084325.html below:

[Python-Dev] Reindenting the C code base?

[Python-Dev] Reindenting the C code base? [Python-Dev] Reindenting the C code base?Antoine Pitrou solipsis at pitrou.net
Sat Dec 13 23:11:47 CET 2008
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.

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.

Regards

Antoine.


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