RetroSearch Browse

Mon Dec 15 22:40:47 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-December/084383.html

On Mon, Dec 15, 2008 at 3:59 PM, Guido van Rossum <guido at python.org> wrote:
> Aha! A specific file. I'm supportive of fixing that specific file. Now
> if you can figure out how to do it and still allow merging between 2.6
> and 3.0 that would be cool.
>

Here's the simplest solution I thought so far to allow smooth merging
subsequently. First, fix the 2.6 version with 4-space indent. Over a
third of the file is already using spaces for indentation, so I don't
think losing consistency is a big deal. Then, block the trunk commit
with svnmerge to prevent it from being merged back to the py3k branch.
Finally, fix the 3.0 version.

-- Alexandre

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

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

[Python-Dev] Reindenting the C code base?