RetroSearch Browse

Tue Jun 3 16:29:32 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-June/080005.html

On Tue, Jun 3, 2008 at 3:48 AM, Georg Brandl <g.brandl at gmx.net> wrote:
> Antoine Pitrou schrieb:
>>
>> Guido van Rossum <guido <at> python.org> writes:
>>>
>>> I'd prefer the 2.6 code base to
>>> stay true to 2.x, and the 3.0 code base start afresh where it makes
>>> sense. We should reindent more of the 3.0 code base to use
>>> 4-space-indents in C code too.
>>
>> Is there any reason reindenting shouldn't be done for 2.6 too?
>> (apart from "staying true to 2.x" :-))
>
> It would make svn blame useless, for a start.
>
> (SVN could really use a feature to exclude certain revisions from
> showing up in svn blame.)

What he said. And "staying true to 2.x" is not a bad rationale. :-)

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

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

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

[Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0