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

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

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

• Previous message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Next message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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" :-))

Antoine.

• Previous message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Next message: [Python-Dev] [Python-3000] Stabilizing the C API of 2.6 and 3.0
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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