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/2008-June/080001.html below:

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

[Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0 [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0Georg Brandl g.brandl at gmx.net
Tue Jun 3 12:48:54 CEST 2008
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.)

Georg

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