«

Hi,

I've a project with tabs and spaces mixed (yes I know it's bad).

I edit each file to remove tabs, but it's so easy to make a mistake.
Do you know a tools to compare the initial file with the cleaned one to
know if the algorithms are the same ?
By comparing pyc files for example.

Thanks.

> I've a project with tabs and spaces mixed (yes I know it's bad).
>
> I edit each file to remove tabs, but it's so easy to make a mistake.
> Do you know a tools to compare the initial file with the cleaned one to
> know if the algorithms are the same ?
> By comparing pyc files for example.

Tools/scripts/reindent.py of the standard Python distribution normalizes
white space in source code. It is used to maintain normalized
indentation in the Python library itself, but you can certainly use it
also for your own files

Regards,
Martin

Le 31/10/2010 13:10, Martin v. Loewis a écrit :
>> I've a project with tabs and spaces mixed (yes I know it's bad).
>>
>> I edit each file to remove tabs, but it's so easy to make a mistake.
>> Do you know a tools to compare the initial file with the cleaned one to
>> know if the algorithms are the same ?
>
> Tools/scripts/reindent.py of the standard Python distribution normalizes
> white space in source code.

So great, you save my time !
Should I be worry about this comment in reindent.py "So long as the
input files get a clean bill of health from tabnanny.py, reindent should
do a good job." ?

Thanks

> Should I be worry about this comment in reindent.py "So long as the
> input files get a clean bill of health from tabnanny.py, reindent should
> do a good job." ?

I don't think so: IIUC, this is about comments that are not reasonably
aligned with preceding or following code lines, most likely, you don't
have such comments in your files.

Regards,
Martin

In message <4ccd5ad9$0$19151$>, jf wrote:

> I edit each file to remove tabs ...

expand -i <oldfile >newfile

> Do you know a tools to compare the initial file with the cleaned one to
> know if the algorithms are the same ?

diff -b oldfile newfile

in 645437 20101031 230912 Lawrence D'Oliveiro <_zealand> wrote:
>In message <4ccd5ad9$0$19151$>, jf wrote:
>
>> I edit each file to remove tabs ...
>
>expand -i <oldfile >newfile
>
>> Do you know a tools to compare the initial file with the cleaned one to
>> know if the algorithms are the same ?
>
>diff -b oldfile newfile

meld

On Mon, 01 Nov 2010 12:09:12 +1300, Lawrence D'Oliveiro wrote:
> In message <4ccd5ad9$0$19151$>, jf wrote:
>
>> I edit each file to remove tabs ...
>
> expand -i <oldfile >newfile
>
>> Do you know a tools to compare the initial file with the cleaned one to
>> know if the algorithms are the same ?
>
> diff -b oldfile newfile

Warning: "diff -b" won't detect changes in indentation. Changes in
indentation can change a Python program.

--
To email me, substitute nowhere->spamcop, invalid->net.

In message <>, Peter Pearson wrote:

> On Mon, 01 Nov 2010 12:09:12 +1300, Lawrence D'Oliveiro wrote:
>
>> In message <4ccd5ad9$0$19151$>, jf wrote:
>>
>>> I edit each file to remove tabs ...
>>
>> expand -i <oldfile >newfile
>>
>>> Do you know a tools to compare the initial file with the cleaned one to
>>> know if the algorithms are the same ?
>>
>> diff -b oldfile newfile
>
> Warning: "diff -b" won't detect changes in indentation. Changes in
> indentation can change a Python program.

I’m getting less and less keen on that particular feature of Python...

On 2010-11-01, Lawrence D'Oliveiro <_zealand> wrote:
> In message <>, Peter Pearson wrote:
>>
>>> diff -b oldfile newfile
>>
>> Warning: "diff -b" won't detect changes in indentation. Changes in
>> indentation can change a Python program.
>
> I'm getting less and less keen on that particular feature of Python...

Why?

Other languages have similar problems if you remove salient bits of
syntax before comparing two source files files.

For exmaple, if you remove all of the curly-braces from two C source
files before comparing them, you don't get useful results.

--
Grant Edwards grant.b.edwards Yow! I'm continually AMAZED
at at th'breathtaking effects
gmail.com of WIND EROSION!!

On Mon, 1 Nov 2010 22:24:03 +0000 (UTC), Grant Edwards wrote:
> On 2010-11-01, Lawrence D'Oliveiro <_zealand> wrote:
>> In message <>, Peter Pearson wrote:
>>>
>>>> diff -b oldfile newfile
>>>
>>> Warning: "diff -b" won't detect changes in indentation. Changes in
>>> indentation can change a Python program.
>>
>> I'm getting less and less keen on that particular feature of Python...
>
> Why?
>
> Other languages have similar problems if you remove salient bits of
> syntax before comparing two source files files.
>
> For exmaple, if you remove all of the curly-braces from two C source
> files before comparing them, you don't get useful results.

True, but diff doesn't come with an "ignore curly braces" option.
I'm not personally repelled by Python's use of significant indentation,
but I must concede that some awkwardness results from assigning
significance to something (whitespace) that many tools are inclined
to treat as insignificant.

--
To email me, substitute nowhere->spamcop, invalid->net.