Deprecate tabs for indenting (was Re: Indenting with tabs vs spaces)

Chris Spencer clspence at one.net
Tue Dec 4 12:48:17 EST 2001


	How many times do people have to point out that you're wrong?

	In my development group, we had people who used spaces while coding
Python, and we had people using tabs.  What we noticed was that in terms of
uniformity of look, the "spacers" inevitably always chose different amounts of
spaces for indentation (one used 2 spaces, another used 3).  In terms of
maintainability it was a nightmare.  And it looks damned ugly.
	When we standardized on the "tabber" method, everything just magically
lined up in the editor.  The spacers defined their tabs to be 2 or 3 spaces in
width so it was comfortable to look at (I choose 8 spaces of width), but all of
the code looked the SAME instead of the crazy mixture we had before.

	Maybe if you only code for yourself you can have total uniformity of
coding style amongst all of your projects.  When you're dealing with several
people on a development project, that "tabber" convention is absolutely "the
Right Thing(tm)".

Chris.


On Mon, 03 Dec 2001 23:46:35 -0000, Steve Lamb <grey at despair.dmiyu.org> wrote:

>On Tue, 4 Dec 2001 01:36:49 -0800, Peter Bismuti <peterb at cortland.com> wrote:
>> I'm on your side.  After following this thread I am more convinced that tabs
>> are a better approach as it allows for a separation of style and content.
>> Each person can view their file with whatever indentation width they prefer
>> (style) without altering the contents of the file (content).
>
>    How many times to I have to point out that style and content cannot be
>separated?




More information about the Python-list mailing list