A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2009-January/084931.html below:

[Python-Dev] Fixing incorrect indentations in C files (Decoder functions accept str in py3k)

[Python-Dev] Fixing incorrect indentations in C files (Decoder functions accept str in py3k)Brett Cannon brett at python.org
Thu Jan 8 19:48:31 CET 2009
On Thu, Jan 8, 2009 at 10:41, Guido van Rossum <guido at python.org> wrote:
> On Thu, Jan 8, 2009 at 10:29 AM, Brett Cannon <brett at python.org> wrote:
>> On Thu, Jan 8, 2009 at 01:52, Raymond Hettinger <python at rcn.com> wrote:
>>> From: "M.-A. Lemburg" <mal at egenix.com>
>>>>
>>>> The question to put up against this is: How often do you get
>>>> irritated by lines not being correctly indented ?
>>>
>>> Basically never.
>>
>> And of course I am the polar opposite: frequently enough that I want
>> to see this fixed.
>
> I'm in the middle -- I don't mind so much if some parts of a file are
> indented using a different style than other parts. But I am adamant
> that local misalignment is horrible. Since mixing tabs and spaces
> within one function is bound to lead to local misalignments (either
> for the folks who set their tabs at 4 or for the folks who set them at
> 8, as God intended), I want at least within each function the
> indentation to be all spaces or all tabs. (And yes, the convention of
> implementing 4-position indents using tabs followed by 4 spaces for
> odd indents is evil, as it looks horrible for folks whose tabs are set
> to 4.)
>

Can we then all agree that a policy of re-indenting per function as
changes are made to the code is acceptable but not required?

-Brett
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